Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

distance_matrix

Calculate distances and travel times between multiple points. Specify an origin and destinations to receive a matrix of distances and durations.

Instructions

Calculate distances and travel times between multiple points. First coordinate is the origin; all others are destinations. Returns a matrix of distances and durations.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, but description adequately discloses the tool's behavior: it calculates distances and durations, returns a matrix. No destructive actions implied. Missing details on limits or authentication, but acceptable for a read-like tool.

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 concise sentences with no unnecessary words. Front-loaded with verb and resource, followed by specific usage and return value.

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?

Given no output schema, the description adequately explains return format (matrix of distances and durations). However, with many sibling tools, adding brief guidance on when to choose this over alternatives would improve completeness.

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?

Schema coverage is 100%, but description adds clarity: 'First coordinate is the origin; all others are destinations' explains the coordinate parameter's semantics beyond the schema. Also clarifies return type, adding value.

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 clearly states the tool calculates distances and travel times between multiple points, specifies the first coordinate as origin, and indicates it returns a matrix. This distinguishes it from siblings like get_directions (turn-by-turn) and distance_matrix_with_traffic (includes traffic).

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?

No explicit when-to-use or comparison with sibling tools. While it implies usage for multiple-point matrices, it does not guide against alternatives like distance_matrix_with_traffic or get_directions.

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