Skip to main content
Glama

Reverse geocode points in batch

reverse_geocode_batch
Read-onlyIdempotent

Batch reverse-geocode up to 20 points in a single request, returning ordered addresses and isolating malformed entries with per-point errors instead of failing the whole call.

Instructions

Reverse-geocode many points in one call, to cut N round-trips down to one.

Accepts at most 20 points; a longer list returns a structured
{"error": "bad_request"} instead of processing anything. Returns one
row per point in `points`, in the same order — each row is whatever
reverse_geocode(lat, lon) returns (address/divisions chain, or a
"divisions_only" degrade — see reverse_geocode's docstring). A
malformed point (missing/non-numeric lat/lon, or a lat/lon out of
range) doesn't fail the whole batch — it yields the standard error
envelope {"lat", "lon", "error": "bad_request", "detail"} in its slot
instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior, and the description adds substantial behavioral detail beyond that: the 20-point limit, whole-batch rejection on overflow, per-point ordering, degrade behavior, and per-slot error envelopes for malformed points. This is exactly the kind of context an agent needs.

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?

The description is front-loaded with the core purpose and then moves through behavior in a logical order: limit, success shape, and error handling. Every sentence adds necessary operational detail without redundancy or filler.

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 batch tool with one parameter, no schema descriptions, and a rich behavioral surface, the description covers the critical execution semantics: limits, ordering, degraded mode, and partial failure behavior. It is complete enough for an agent to invoke the tool correctly without needing additional documentation.

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

Parameters5/5

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

Input schema coverage is 0%, so the description carries the full burden. It explains that `points` is a list of points with lat/lon, imposes a batch size limit, defines what counts as malformed, and describes how each point is processed and returned. This compensates fully for the schema's lack of detail.

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 opens with a specific verb and resource: 'Reverse-geocode many points in one call.' It clearly distinguishes this batch tool from the single-point reverse_geocode sibling by emphasizing the batching behavior and round-trip reduction.

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

Usage Guidelines5/5

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

The description explicitly frames the tool for 'many points' and says its purpose is to cut N round-trips down to one, giving a clear when-to-use signal. It also references reverse_geocode as the per-point behavior source, which implicitly identifies the alternative for single-point use.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chuofringer/placeroot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server