mappls-mcp

get_directions_with_traffic

Get directions with traffic-aware travel times. Input origin and destination as coordinates to receive predictive ETA based on current traffic conditions.

Instructions

Get directions with real-time traffic-aware ETA. Returns predictive travel time based on current traffic conditions.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "get_directions_with_traffic"
  }
}

Input Schema

Name	Required	Description
`origin`	Yes	Start point as 'lat,lng'
`profile`	No	Travel mode (default: driving)
`destination`	Yes	End point as 'lat,lng'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jul 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Discloses that ETA is based on current traffic conditions but does not expand on behavior such as whether it is read-only, API limits, or handling of traffic data unavailability. No annotations are present to supplement this. Minimal additional context beyond the name.

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, front-loaded with key information, no extraneous text. Highly concise and well-structured.

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?

No output schema exists; description only mentions ETA but not the full response structure (e.g., steps, distance). However, given the tool's simplicity and the sibling differentiation via name, it is reasonably complete. Could describe return format for full clarity.

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?

All three parameters have descriptions in the schema (100% coverage), so the description does not need to add extra meaning. Baseline 3 is appropriate as description does not elaborate beyond schema.

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 provides directions with real-time traffic-aware ETA, distinguishing it from the sibling 'get_directions' which likely lacks traffic. The verb 'get' and resource 'directions with traffic' are specific.

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?

Description implies usage when traffic-aware ETA is needed but does not explicitly state when to use this tool versus alternatives like 'get_directions' (without traffic). No exclusion criteria or prerequisites are provided.

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

Deploy Server