Skip to main content
Glama
Sign In
ThinAir Geo

ThinAir Geo

Official
by ThinAirTelematics
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Hybrid

map_match

Snap raw GPS traces to the road network and retrieve the actual driven route with matched geometry, distance, time, road names, and confidence score.

Instructions

Snap a raw GPS trace (2-100 points) to the road network and return the road-accurate route actually driven: matched geometry, distance, time, road names, and a 0-1 confidence. For planning a route between places use directions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Describes input constraints (2-100 points) and output details. Lacks mention of rate limits or side effects, but no annotations exist.

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 convey function, constraints, output, and alternative. No redundancy.

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 input constraints and output elements. No output schema, but description compensates. Could mention error handling or result structure.

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?

Even though there are no explicit parameters, the description explains the input 'raw GPS trace' with point range. Schema coverage is trivial.

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 snaps GPS traces to road network and returns route data. Distinguishes from directions tool.

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 mentions alternative 'directions' for route planning. Could be more specific about other siblings like trace_attributes.

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