Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Reverse Geocode

reverse_geocode

Retrieve place details from latitude/longitude coordinates or an ID to resolve locations into address or place information.

Instructions

Get place information from ID or latitude/longitude:

To obtain infos via ID make sure to pass the following format: {"type": "id", "id": ""}

To obtain infos via lat/long, make sure to provide the following format: {"type": "coordinates", "lat": "", "long": ""}

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": {
      "type": "<type>",
      "id": "<id>",
      "lat": "<lat>",
      "long": "<long>"
    },
    "name": "reverse_geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesstring required only for type=id
latYesthe latitude number($float) example: 41.289294
longYesthe longitude number($float) example: 13.2349029
typeYesrequired, can be "coordinates" or "id"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond input shaping: no authentication requirements, no rate limits, no failure modes, no note on what happens if 'type' mismatches the supplied fields. The only behavioral hint is that the tool dispatches on the 'type' discriminator, which the schema already implies.

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

Conciseness4/5

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

The purpose statement is front-loaded and the two mode blocks are short and parallel, so an agent can parse it quickly. There is minor redundancy in the repeated 'make sure to pass/provide the following format' phrasing and the JSON snippets duplicate structure the schema already encodes, but nothing is padded.

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

Completeness3/5

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

With no output schema and no annotations, the description should say something about what 'place information' actually contains and how misses are signaled; instead it stops after input formatting. It is sufficient for an agent to construct a valid call, but leaves the return contract entirely opaque for a four-parameter lookup tool.

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% and would justify a baseline 3, but the description earns above that by resolving a real ambiguity: the schema marks all four parameters as required, while the description makes clear that id is only relevant for type=id and lat/long only for type=coordinates, and shows the exact literal payload for each. That is meaning-additive beyond the schema field text.

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?

The description opens with a specific verb+resource: get place information from either an ID or latitude/longitude, which is a clear statement of what the tool returns. It distinguishes itself from the sibling 'geocode' implicitly through the reverse-lookup framing, but never states that contrast explicitly, so it lands just short of a 5.

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?

It clearly explains the two invocation modes and the payload shape each requires, which is real usage help. However, it gives no guidance on when to prefer this over the sibling 'geocode' tool or over any other lookup mechanism, and no prerequisites or error conditions are mentioned.

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