Geloky Geocoding

Address of a point

reverse_geocode

Read-onlyIdempotent

Find the street address at a latitude/longitude point. Costs $0.001. For several points use batch_reverse_geocode.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "reverse_geocode"
  }
}

Input Schema

Name	Required	Description	Default
`latitude`	Yes	Latitude in decimal degrees (WGS84).
`longitude`	Yes	Longitude in decimal degrees (WGS84).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds a genuinely new behavioral fact the annotations do not carry: per-call cost of $0.001, which matters for an agent deciding whether to loop. It does not describe the returned address structure, but that is the main remaining gap.

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?

Three short sentences, each doing a distinct job: what it does, what it costs, and which sibling to use instead. Purpose is front-loaded and there is no filler wording.

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 only two parameters and full schema coverage, little documentation is required, and no output schema exists so return values need not be described. However, the description never hints at what comes back (a formatted address string vs. structured components) or how to handle a point with no address, leaving an agent to discover that at call time.

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 description coverage is 100% and both parameters document WGS84 decimal degrees with valid ranges, so the schema carries all parameter semantics. The description restates 'latitude/longitude point' but adds no format, precision, or coordinate-system detail beyond what the schema already says. Baseline 3 applies.

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?

States a specific verb and resource: 'Find the street address at a latitude/longitude point.' The direction (reverse vs forward geocoding) is unambiguous from the name-plus-description pairing, so an agent can separate it from geocode/route siblings without reading the schema.

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?

Explicitly routes the bulk case: 'For several points use batch_reverse_geocode.' That is a concrete alternative with a selecting condition. It stops short of a full when/when-not treatment (e.g., no note that this is the inverse of geocode or any coverage caveats), so 4 rather than 5.

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

All Geloky Geocoding tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?