MapmyIndia Mappls MCP Server

Mappls Distance Matrix

mappls_distance_matrix

Compute a matrix of travel distances and durations between multiple origin and destination points in India. Choose driving, biking, walking, or trucking profiles for route planning.

Instructions

Calculate travel distances and durations matrix between multiple origin and destination points in India.

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": {
      "origins": "<origins>",
      "destinations": "<destinations>"
    },
    "name": "mappls_distance_matrix"
  }
}

Input Schema

Name	Required	Description	Default
`origins`	Yes	List of origin coordinate strings ["lng1,lat1", "lng2,lat2"] or eLocs.
`profile`	No	Transport profile mode: "driving", "biking", "walking", or "trucking". Default is "driving".	driving
`destinations`	Yes	List of destination coordinate strings ["lng1,lat1", "lng2,lat2"] or eLocs.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only adds the geographic constraint 'in India' and the implied read-only nature of 'Calculate'. It does not disclose potential API limitations, error behavior, or any other operational traits.

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 concise sentence that front-loads the core action and resource, with no wasted words. It efficiently conveys the essential purpose and scope.

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

Completeness3/5

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

The schema and output schema cover parameter details and return structure, but the description lacks explicit usage guidance and behavioral context beyond the basic purpose. For a relatively simple tool, this is adequate but not complete; an agent would benefit from knowing when this tool outranks get_directions or snap_to_road.

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?

The input schema provides 100% coverage of origin, destination, and profile parameters, including coordinate format and default values. The description adds no parameter-specific detail beyond what the schema already contains, so the baseline of 3 is appropriate.

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 specific verb ('Calculate') and resource ('travel distances and durations matrix'), clearly distinguishing it from sibling tools like get_directions, which focuses on individual routes, and geocoding tools. The geographic scope ('in India') adds further precision.

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 phrase 'between multiple origin and destination points' implies the tool is suited for matrix-style requests rather than single-route calculations, giving some context. However, it does not explicitly mention when to prefer this over siblings like get_directions or mention any exclusions or prerequisites.

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

Deploy Server