/mcp/tools

MCP tools, resources, and prompts

Mireye’s MCP surface: four tools, catalog resources, and workflow prompts.

Tools

{
  "tool": "mireye_ask",
  "arguments": {
    "lat": 40.7128,
    "lng": -74.0060,
    "question": "What is the elevation here?"
  }
}

{
  "tool": "mireye_fetch",
  "arguments": {
    "lat": 29.7604,
    "lng": -95.3698,
    "preset": "flood_risk"
  }
}

JSON

{
  "tool": "mireye_geocode",
  "arguments": {
    "address": "350 5th Ave, New York, NY 10118"
  }
}

address_too_coarse — the address only resolved to a ZIP/city/county centroid. Do not retry; ask the user for a street number. The upstream answers 200 with a city centroid for a nonexistent address, so this rejection is what stands between a typo and a confidently wrong answer.
address_not_found — no match at all. Also not retryable.

{
  "tool": "mireye_lookup",
  "arguments": {
    "input": "480 Berdoll Ln, Cedar Creek TX"
  }
}

resolved — a coordinate and confidence, plus a parcel block when the geocode cleared parcel-quality accuracy. Also carries free area/hazard/ market context gathered concurrently with the parcel lookup: jurisdiction codes (state, block/block-group, congressional district, CBSA/metro area), elevation, FEMA flood-zone fields, a county_market bundle, Opportunity Zone status, and timezone — see POST /v1/lookup’s full contract for the complete field list. Every one degrades independently to null on its own failure.
clarify — genuinely ambiguous. Present candidates to the user; never auto-pick one.
no_match — an honest failure with a reason (e.g. apn_not_supported_in_v1 for APN-only input, which isn’t supported yet).