Skip to main content
Glama
Sign In
ThinAir Geo

ThinAir Geo

Official
by ThinAirTelematics
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Hybrid

distance_matrix

Compute road distances and travel times for multiple origin-destination pairs. Supports free-text addresses or coordinates, capped at 625 pairs. Ideal for fleet dispatch, nearest depot, and bulk ETA tables.

Instructions

Compute road distances and travel times for every origin -> destination pair. Endpoints accept free-text addresses or 'lat,lon'; N x M is capped at 625 pairs. Use for fleet dispatch, nearest-depot, and bulk ETA tables.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Discloses the 625-pair cap, a key behavioral constraint. No annotations provided, but description adds value by mentioning the limit. Does not mention rate limits or cost.

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, front-loaded with core purpose. Every word earns its place.

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

Completeness3/5

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

No output schema, so description should clarify return format (e.g., units, structure). Mentions 'road distances and travel times' but not detailed enough for complex use.

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?

No parameters in input schema, so description has no need to explain them. Baseline 4 for 0 params; schema coverage is 100% trivially.

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?

Clearly states the tool computes road distances and travel times for origin-destination pairs, using free-text addresses or lat,lon. Distinguishes from siblings like directions (step-by-step) and traffic.

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?

Provides explicit use cases: fleet dispatch, nearest-depot, bulk ETA tables. Lacks explicit when-not or alternatives, but context implies directions for step-by-step.

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

Deploy Server

Other Tools