ThinAir Geo

Official

by ThinAirTelematics

Overview Schema Source Related Servers Discussions(1)Admin

JavaScript

Hybrid

place_get

Retrieve place details (name, label, layer, coordinates) using a stable ThinAir ID from geocoding or search results.

Instructions

Look up a place by its stable ThinAir id (ta_place_... / ta_intersection_...) as returned in the id field of geocode, reverse_geocode, search_places, or resolve_intersection. Returns canonical name, label, layer, and coordinates.

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": "place_get"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Jul 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Describes a read-only lookup operation with no side effects. It discloses return fields. With no annotations provided, the description adequately covers the behavior for a simple query tool, though it omits rate limits or authentication details which are less critical here.

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, front-loaded with the core purpose, efficient and no wasted words. Every word 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 no output schema, the description sufficiently explains the return values. The tool is simple and the description covers all essential aspects for an agent to use it correctly.

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 input schema is empty (0 parameters), so description cannot add value beyond schema. Per calibration, no params baseline is 4. Description correctly lists return fields, which is helpful.

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 looks up a place by its ThinAir ID, lists the source tools that return such IDs, and specifies the output fields (canonical name, label, layer, coordinates). It effectively distinguishes from siblings like reverse_geocode and geocode.

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 describes when to use (when you have a ThinAir ID from specific tools) and what to expect. While it doesn't state when not to use, the context is clear enough for an agent to infer alternatives.

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