ThinAir Geo

geocode

Read-onlyIdempotent

Convert an address, place name, street, or intersection into coordinates and structured location results. Use when input is text and you need coordinates before routing, weather, or search. Supports street-level resolution and proximity biasing.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Number of candidates to return (default 5, max 40)
`query`	Yes	Address, place name, street, intersection (e.g. 'Broadway and 42nd Street New York'), or free-form location text
`layers`	No	Restrict to: address, street, venue, locality. Use layers=street when user clearly wants a street entity. Use layers=venue for stadiums, monuments, parks, and named POIs (e.g. 'Minute Maid Park', 'Lambeau Field', 'Statue of Liberty') — bypasses address-parser tokenization that otherwise resolves venue+state to the state region centroid
`focus_lat`	No	Bias results near this latitude — use when user says 'near me' or 'close to'
`focus_lon`	No	Bias results near this longitude
`boundary_country`	No	ISO country code to reduce ambiguity (alpha-2 or alpha-3)

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No
`geojson`	No
`metrics`	No
`summary`	No	Map of scalar facts the LLM should surface verbatim
`precision`	No
`display_hint`	No

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds useful behavioral context beyond these: street-level resolution and proximity biasing. This helps the agent understand capabilities not captured in the annotations. No contradictions.

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 three well-structured sentences: the first states the primary function, the second gives the canonical use case, and the third highlights additional capabilities. No fluff or repetition, every sentence earns its place.

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?

Given the rich input schema, detailed parameter descriptions, existing annotations, and output schema, the description covers the tool's purpose, usage context, and key behaviors sufficiently. The agent has everything needed to select and invoke the tool correctly without needing additional return-value explanation.

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?

The input schema provides 100% coverage of all 6 parameters with detailed descriptions, so the baseline is 3. The description adds only a high-level mention of 'proximity biasing' and 'street-level resolution' which loosely map to focus_lat/focus_lon and layers, but does not detail parameter syntax beyond what the schema already provides.

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 clearly states the tool converts addresses, place names, streets, or intersections into coordinates and structured location results. It uses a specific verb with a precise resource and output, and implicitly distinguishes itself from siblings like geocode_structured (structured input) and reverse_geocode (coordinates to address).

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?

The description explicitly states when to use the tool: when input is text and coordinates are needed before routing, weather, or search. However, it does not name alternative tools or provide explicit when-not conditions, though 'Use when input is text' implies structured input should go elsewhere.

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

All ThinAir Geo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose. Overlapping tools (geocode vs geocode_structured, explore vs search_places, map_match vs trace_attributes) are explicitly differentiated in their descriptions, with cross-references guiding correct selection. No two tools appear to do the same thing.

Naming Consistency4/5

Most tools follow a predictable verb_noun pattern (geocode, reverse_geocode, batch_geocode, search_places, resolve_intersection), but there are minor deviations: some tools use noun-only names (directions, traffic, weather) and a couple use noun_verb order (place_get, geofence_contains). This creates slight inconsistency but remains readable.

Tool Count4/5

At 19 tools, the set is slightly heavy but each tool earns its place by covering a distinct geospatial function. The breadth spans geocoding, routing, places, telematics, geofencing, traffic, weather, and account management, making the count reasonable for a comprehensive geo API.

Completeness5/5

The tool surface is remarkably complete for a geospatial server: forward, reverse, batch, structured, and intersection geocoding; routing, matrix, and isochrones; place search, exploration, and ID lookup; map matching, trace attributes, and point snapping; plus geofencing, traffic, weather, and quota management. No critical gaps or dead ends apparent.

Resources

Need Help?