Skip to main content
Glama
Sign In
ThinAir Geo

ThinAir Geo

Official
by ThinAirTelematics
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Hybrid

trace_attributes

Retrieve per-segment road attributes (name, class, speed limit, surface, truck route, length) for a GPS trace of 2-100 points, along with a matcher confidence score.

Instructions

Return per-segment road/network attributes for a matched GPS trace (2-100 points): road names, classes, speed limits, surfaces, truck-route flags, and segment lengths, plus a matcher confidence score. For just the matched route line use map_match.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so description carries full burden. It mentions the output content and point range constraint but fails to explain how the input trace is supplied since the input schema is empty. This missing detail on input mechanism harms transparency.

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, concise and front-loaded. First sentence enumerates output details, second sentence offers alternative tool. No wasted words.

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

Completeness2/5

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

Given no annotations and no output schema, the description should explain both input and output. It explains output well but omits how the trace input is provided (no parameters, no reference to prior calls). This is a significant gap for an agent to use 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?

There are no parameters, so baseline is 4. Description adds no parameter information because none exist, which is acceptable.

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?

Description clearly states the tool returns per-segment road/network attributes for a matched GPS trace, listing specific attributes. It distinguishes itself from sibling map_match by noting that for just the matched route line, use map_match.

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 states when to use (to get attributes for a matched GPS trace) and when not to use (if only need the route line, use map_match). Provides clear alternative.

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