MapmyIndia Mappls MCP Server

Mappls Place Details

mappls_place_details

Retrieve rich location attributes and details for a place by entering its 6-character Mappls eLoc code. Get comprehensive place information for India.

Instructions

Retrieve rich location attributes and details for a location using its 6-character Mappls eLoc code.

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": {
      "eloc": "<eloc>"
    },
    "name": "mappls_place_details"
  }
}

Input Schema

Name	Required	Description	Default
`eloc`	Yes	The 6-character alphanumeric Mappls eLoc identifier (e.g. "MMI123" or "DEL110").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a non-destructive read via 'Retrieve', but does not disclose error behavior, invalid eLoc handling, authentication needs, rate limits, or response characteristics. This is a significant gap for a tool with zero annotation coverage.

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, well-structured sentence that states the action, object, and required input format without any filler. Every word contributes meaning and no information is buried.

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?

For a one-parameter lookup with an output schema, the description is adequate at a basic level, but it lacks sibling differentiation and behavioral context that would help an agent confidently choose and call this tool. It is minimally viable, not fully complete.

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 description coverage is 100% and the schema already documents the eloc parameter with format and examples. The description adds no new parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 ('Retrieve'), names the resource ('rich location attributes and details'), and identifies the unique key ('6-character Mappls eLoc code'). This clearly separates it from sibling tools like geocode or reverse_geocode, which use addresses or coordinates instead of eLocs.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as mappls_autosuggest or mappls_geocode. The only implied usage is that the caller must have an eLoc, but no explicit conditions or exclusions are stated.

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

Deploy Server