MapmyIndia Mappls MCP Server

Mappls Reverse Geocode

mappls_reverse_geocode

Convert latitude and longitude coordinates into a formatted address and administrative details for any location in India.

Instructions

Reverse geocode a pair of geographic coordinates (latitude and longitude) to get the corresponding formatted address and administrative details.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "mappls_reverse_geocode"
  }
}

Input Schema

Name	Required	Description	Default
`latitude`	Yes	The latitude coordinate (e.g. 28.6139).
`longitude`	Yes	The longitude coordinate (e.g. 77.2090).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It clearly identifies the operation as a read-only lookup ('get') and tells the agent what kind of result to expect: formatted address plus administrative details. It does not describe edge cases or coordinate-system assumptions, but it doe disclose the core behavior without contradiction.

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 sentence that starts with the action, names the exact inputs, and states the outcome. There is no filler or repetition; every part of the sentence contributes to understanding what the tool does.

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 low complexity tool with two fully documented parameters and an existing output schema, the description covers the essential invocation context. The only notable omission is explicit guidance about selecting this tool over its sibling geocoding tools, which is handled separately under usage guidelines.

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 with descriptions and examples, achieving 100% coverage. The description adds no new parameter-level meaning beyond naming latitude and longitude, so the baseline of 3 applies.

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?

Th description clearly states a specific verb-resource action: reverse geocoding coordinate pairs into formatted addresses and administrative details. It is unambiguous about what the tool does, though it does not explicitly contrast itself with the sibling mappls_geocode or other address-related tools.

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 the natural use case: when you have latitude and longitude and need an address. However, it does not explicitly state when to prefer this tool over mappls_geocode, mappls_reverse_geocode sibling alternatives, nor when not to use it.

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

Deploy Server