mireye_ask and mireye_fetch. Catalog discovery is exposed as MCP
resources, and common workflows are exposed as prompts, so agents get better
context without paying for extra tool-choice clutter.
Tools
If the caller asked a question, useBoth tools are read-only and idempotent. Their schemas constrain latitude and longitude to the supported US envelope and capmireye_ask. If the caller named fields or a preset, usemireye_fetch.
fields at 50 items.
mireye_ask
Answers a natural-language question about a US coordinate with citations to
authoritative federal data sources.
mireye_fetch
Fetches exact catalog fields or preset bundles with per-field provenance.
Resources
Use resources for read-only catalog context instead of adding catalog tools:
The hosted MCP endpoint serves these from the same in-memory payload as
GET /v1/meta/fields. The local stdio adapter fetches that endpoint and
caches it for one hour with ETag support.
Prompts
Prompts package common agent workflows while leaving the two tool names stable:Errors
MCP tool failures include actionable JSON fields such ascode, message,
http_status, request_id, tool, and retryable. Agents should retry only
when retryable is true, refresh catalog context for fields_unknown, and ask
the user to authenticate for mcp_auth_required.
See /api-reference/errors for the HTTP API error
catalog and /api-reference/fetch for preset semantics.