MapmyIndia Mappls MCP Server

Mappls Geocode

mappls_geocode

Geocode any Indian address or landmark to obtain latitude, longitude, eLoc code, and standardized address details.

Instructions

Geocode an address or location text to retrieve latitude, longitude, eLoc code, and standardized address details 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": {
      "address": "<address>"
    },
    "name": "mappls_geocode"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No	Country region filter (default: "IND" for India).	IND
`address`	Yes	The target address, city, landmark, or location query string (e.g. "Connaught Place, New Delhi" or "Electronic City, Bengaluru").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that this is India-focused geocoding and that results include standardized address details and eLoc codes, but it does not mention limits, edge cases, or any special behavior. The read-only nature of geocoding is reasonably clear from the tool name and description.

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, efficient sentence that front-loads the action and captures the resource, geographic scope, and key return values. There is no filler or redundant phrasing.

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?

For a two-parameter tool with complete schema documentation and an output schema, the description is largely sufficient. The main missing piece is explicit guidance on when to use this instead of closely related location tools.

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 already documents both parameters clearly with an example for address and a default for region, so the description adds little beyond restating the output. With 100% schema description coverage, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource — 'Geocode an address or location text' — and names concrete outputs: latitude, longitude, eLoc code, and standardized address details. It does not explicitly contrast with siblings like mappls_autosuggest or mappls_text_search, but the forward-geocoding intent is unmistakable.

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 usage through examples like 'Connaught Place, New Delhi', but it never states when to choose this tool over alternatives such as mappls_autosuggest or mappls_text_search. The intended context is inferable but not explicit.

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

Deploy Server