← The MCP server

MCP tools reference

Every InstaMaps tool: what it is for, when another fits better, its inputs, its sources and their dates, what has been measured, and a real answer from the live server.

For agents: the whole reference in one fetch, as text or JSON.

What every answer guarantees

  • Nothing is dropped: every row sent comes back, in order, under your own id; rows that cannot be placed or answered say why. An answer that would lose rows fails loudly instead.
  • Every row carries confidence {level: high | medium | low, score, basis}; basis is a stable code (rooftop, postcode_centre, not_placed…) and the answer's confidence object says what each basis present means and what to do about it.
  • Every row carries record_key, the same place ID from every tool, so answers from different tools join on it.
  • Every answer ends with a run block: when, how many rows, sources with their dates, the confidence counts, calls used and left today, and a run_id that any tool can take as source {run} and render_map as from_run.
  • Lists by reference: pass a Google Sheet, a Drive file or a run_id instead of typing rows. Every tool but one only reads; write_to_sheet puts an answer into the sheet as new dated columns or a new tab, never overwriting.
  • No vendor or model names in answers; every source is named with its date.

Free: 5,000 tool calls a day per person, reset at midnight UTC; a call counts once however many rows it carries; a sheet by reference is one call; checking a job is free.

Facts and risk