geocode_by_idRe-fetch a MapTiler geocoding feature by its stable ID (returned in geocode / geocode_reverse results). Use to refresh or re-localize a previously discovered place.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| language | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "id": "aplace123456"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and not destructive. Description adds functional context (re-fetching by stable ID) that aligns with these hints, reinforcing the safety profile without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences, front-loaded with the action. No redundant or extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple tool with 2 params, no output schema, and rich annotations, description covers purpose and usage but lacks parameter explanations. Adequate but could be enhanced by describing the 'language' parameter.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage for parameters. Description mentions 'stable ID' as concept but does not explain the 'id' or 'language' parameters, leaving their meaning and format unclear. Minimal value added beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (re-fetch) and resource (geocoding feature by stable ID), and distinguishes from sibling tools geocode and geocode_reverse by specifying that the ID comes from those results.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'use to refresh or re-localize a previously discovered place', indicating when to use. Implicitly excludes initial geocoding by referencing prior results, but no explicit when-not-to-use or alternative names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.