Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

address_analytics

Analyze and standardize raw Indian addresses by breaking them into structured components such as house number, street, locality, district, state, and pincode.

Instructions

Analyze and standardize an Indian address — breaks it into structured components (house number, street, locality, district, state, pincode).

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

Input Schema

NameRequiredDescriptionDefault
addressYesRaw address string to analyze and standardize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/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. It clearly indicates a read-only analytics operation without side effects. However, it lacks details on authorization, rate limits, or output format, though the listed components give a reasonable expectation.

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 efficiently conveys the purpose and output. It is front-loaded with the action and resource, and every word adds value.

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

Completeness5/5

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

Given the tool has only one parameter and no output schema, the description is sufficiently complete. It explains the input, processing, and expected output components, leaving no major gaps for an agent to misunderstand.

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?

The single parameter 'address' is fully described in the input schema. The tool description adds the crucial context that the address must be an Indian address, which is not present in the schema's parameter description. This helps the agent understand the tool's scope.

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's purpose: analyze and standardize an Indian address into structured components. It uses a specific verb ('analyze and standardize') and resource ('Indian address'), and the resulting components are explicitly listed. This differentiates it from sibling tools like geocode or validate_pincode.

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 tool is for parsing Indian addresses, but it does not provide explicit guidance on when to use it versus alternatives (e.g., geocode or validate_pincode). No when-not-to-use or prerequisite information is given.

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