ThinAir Geo

Official

Overview Schema Source Related Servers Discussions(1)Admin

geocode_structured

Geocode address using individual components like street, city, region, and postal code. Ideal for structured data from forms or databases, skipping free-text parsing.

Instructions

Geocode from discrete address components (address, locality, region, postalcode, country) instead of one free-text string. Use when input is already fielded (forms, CRM, stop tables) — skips free-text parsing. At least one component required. For named intersections use resolve_intersection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "geocode_structured"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Jul 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, but description adds constraint (at least one component required) and implies no side effects. It adds value beyond schema which has no parameters.

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?

Two sentences, no fluff. First sentence states purpose and components, second provides usage guidance and constraint. Front-loaded and efficient.

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

Completeness4/5

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

Given no output schema and no annotations, description covers purpose, usage, alternatives, and constraint. Missing return format but adequate for a simple geocoding 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?

Input schema has zero parameters, so baseline is 4. Description lists components (address, locality, region, postalcode, country) but lacks format details. Still adds meaning beyond empty schema.

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 verb (geocode), resource (discrete address components), and differentiates from free-text geocoding and resolve_intersection. This provides specific verb+resource with sibling differentiation.

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?

Explicitly indicates when to use (fielded input from forms, CRM, stop tables) and suggests an alternative (resolve_intersection for named intersections).

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