Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Geocode

geocode

Converts a formatted address into place details by querying Openapi.com, helping users retrieve location information from street, city, postal code, and country input.

Instructions

Retrieve informations about a place supplying address.

To improve success of results, use the format: [street], [city] [postal code] [country].

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": {
      "address": "<address>"
    },
    "name": "geocode"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesstring

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?

With no annotations, the description carries the full behavioral burden, yet it never says what 'information' is returned (coordinates, normalized address, structured components), whether lookups require auth or are rate limited, or how failures/ambiguous matches are reported. The only behavioral insight is that a formatted address improves success — useful, but thin for an unannotated tool.

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?

Two short sentences, purpose first and format tip second, with no padding. Minor wording issues ('informations') do not impede comprehension.

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?

For a one-parameter tool with no output schema and no annotations, the definition should at least characterize the return payload and its counterpart (reverse_geocode). The input side is well covered; the output and behavioral side are not.

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?

The single address parameter has full schema coverage (though its schema text is just 'string'). The description adds real value beyond that by specifying a recommended composite format, which directly affects call quality.

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 states a specific verb and resource: retrieve information about a place by supplying an address. That is a clear geocoding purpose, but it never contrasts with the sibling reverse_geocode, so the agent must infer the direction of the mapping from the name alone.

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 gives useful input-format guidance ('[street], [city] [postal code] [country]') to improve result quality, which is a form of usage instruction. It does not say when to prefer this over reverse_geocode or what happens if the address is partial or ambiguous.

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