Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

distance_matrix_with_traffic

Calculate distances and travel times with real-time traffic data between multiple coordinates. Supports driving, trucking, biking, and walking profiles.

Instructions

Calculate distances and traffic-aware ETAs between multiple points using real-time traffic data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coordinates": "<coordinates>"
    },
    "name": "distance_matrix_with_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoTravel mode (default: driving)
coordinatesYesSemicolon-separated lat,lng points (min 2). e.g. '28.55,77.13;28.48,77.05'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It states the tool uses real-time traffic data but does not disclose the output format (e.g., matrix of distances/durations), any rate limits, or cost implications. The read-only nature is implied but not explicit.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the core purpose.

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 the complexity of the tool (multiple points, traffic data) and the absence of an output schema or annotations, the description is too brief. It fails to explain the output structure (e.g., matrix format) or important constraints like maximum number of points.

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?

Schema coverage is 100%, so baseline is 3. The description adds the context of 'real-time traffic data' but does not enhance understanding of the parameters beyond what the schema already provides. The schema already describes the coordinates format and profile enum.

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 uses a clear verb ('Calculate') and specific resource ('distances and traffic-aware ETAs between multiple points'), distinguishing it from siblings like 'distance_matrix' (no traffic) and 'get_directions_with_traffic' (single route directions).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for multiple points with traffic data but does not explicitly state when to use this tool over alternatives or mention any prerequisites or limitations. No 'when not to use' guidance is provided.

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