Skip to main content
Glama
ThinAirTelematics

ThinAir Geo

Official
by ThinAirTelematics
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

batch_geocode

Geocode multiple addresses, intersections, or place queries in one request with structured per-record results. Use for bulk operations instead of repeated single geocode calls.

Instructions

Geocode multiple addresses, intersections, or place queries in one request with structured per-record results. Use for bulk operations instead of repeated single geocode calls. Max 50 per batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • bin/server.js:74-79 (registration)
    Registration of the batch_geocode tool in the static tool catalog. This is a local reference adapter that does not execute the tool — it only lists it in tools/list and returns a redirect message on tools/call pointing to the hosted endpoint at https://geo.thinair.co/mcp. The actual handler logic is on the remote server.
    {
  name: "batch_geocode",
  description:
    "Geocode multiple addresses, intersections, or place queries in one request with structured per-record results. Use for bulk operations instead of repeated single geocode calls. Max 50 per batch.",
  inputSchema: { type: "object" },
},

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

Discloses structured per-record results and max batch size, but lacks details on output format, error handling, or rate limit implications. With no annotations, more behavioral context would be beneficial.

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 concise sentences, front-loaded with the primary action, and no unnecessary words.

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?

Covers purpose, usage guidance, and batch limit. Lacks input format details and output schema, but given the tool's simplicity and sibling context, it is largely adequate.

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 is empty, so the description adds meaning by mentioning addresses, intersections, or place queries. However, it does not specify how to structure these inputs, leaving ambiguity.

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 geocodes multiple addresses, intersections, or place queries in one request, distinguishing it from the sibling 'geocode' tool which handles single requests.

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 advises to use for bulk operations instead of repeated single geocode calls, and specifies a batch limit of 50.

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

Install Server

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/ThinAirTelematics/thinair-geo'

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