Maps by DeltaBreen

poi_details

Read-only

Fetch one landmark / point of interest by its Wikidata id (from a search_pois or pois_nearby result): name, coordinates, category, description and image. Counts one lookup against the workspace's monthly searches, on every plan.

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": {
      "wikidata_id": "<wikidata_id>"
    },
    "name": "poi_details"
  }
}

Input Schema

Name	Required	Description	Default
`key_id`	No	The map key (uuid from list_keys) to count the lookup against. Default: the workspace's first active secret key, else its first publishable one.
`wikidata_id`	Yes	The POI's Wikidata id (from a search or nearby result), e.g. "Q243".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.3/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 description does not need to restate safety. It adds meaningful non-annotation context by disclosing that each call consumes one lookup from the workspace's monthly searches on every plan, which matters for cost-sensitive agents.

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?

A single, front-loaded sentence that states purpose, provenance of the identifier, return fields, and billing impact with no filler. Every clause carries information an agent needs.

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

Completeness5/5

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

For a simple two-parameter lookup with no output schema, the description supplies the missing return-value summary and the quota cost. Combined with full schema coverage and clear annotations, an agent has everything needed to invoke it correctly.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented in the schema, including where the Wikidata id comes from and the default key behavior. The description restates the id provenance slightly but adds no new syntax or constraints beyond what the schema provides.

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

Purpose5/5

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

The description names a specific verb (fetch), resource (one landmark/POI), and identifier type (Wikidata id), and enumerates the returned fields (name, coordinates, category, description, image). It explicitly distinguishes itself from search_pois and pois_nearby by stating the id must come from one of those results.

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

Usage Guidelines4/5

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

It clearly establishes the usage context: call this after search_pois or pois_nearby, using an id from those results. There is no explicit when-not guidance or mention of alternatives for other lookup paths, but the primary flow is unambiguous.

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?