Maps by DeltaBreen

search_pois

Read-only

Look up a landmark / point of interest by name (e.g. "Eiffel Tower") and get the matching places with coordinates, category and an image where one exists, most prominent first. autocomplete=true is a fast prefix match, free within the same daily type-ahead; the default is a full search that counts one lookup against the workspace's monthly searches, on every plan. Past the plan it returns searches_exhausted and nothing is charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_pois"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	The landmark name to look up, e.g. "Colosseum". 2 to 80 characters (1 for autocomplete).
`limit`	No	How many results to return, 1 to 10. Default 5.
`key_id`	No	The map key (uuid from list_keys) to count the search against. Default: the workspace's first active secret key, else its first publishable one.
`autocomplete`	No	A fast prefix match for a type-ahead, free within the same daily type-ahead as search_places and counted past it. Default (false) is a full, counted search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavioral context: searches count against a monthly quota, autocomplete is free within the daily type-ahead, and exhaustion returns searches_exhausted without charging.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool returns before explaining the billing-sensitive autocomplete mode. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers return shape, ordering, billing, and quota-exhaustion behavior, which is sufficient for a read-only search tool with no output schema. Minor gaps remain around empty-result behavior and explicit sibling routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by clarifying the cost model of autocomplete and the prominence ordering of results. It does not go beyond the schema on limit or key_id semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Look up a landmark / point of interest by name') and describes the returned fields (coordinates, category, image, prominence order). It does not explicitly distinguish itself from sibling search_places, so an agent must infer the division of labor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the autocomplete-versus-full-search tradeoff and its billing implications, which is useful within-tool guidance. However, it gives no explicit guidance on when to choose this tool over search_places, poi_details, or pois_nearby.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Maps by DeltaBreen tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?