Skip to main content
Glama
Sign In
mappls-mcp

mappls-mcp

by AmanMakesStuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

validate_pincode

Validate a 6-digit Indian pincode to retrieve its associated district, city, and state information.

Instructions

Validate an Indian 6-digit pincode and get the associated district, city, and state information.

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": {
      "pincode": "<pincode>"
    },
    "name": "validate_pincode"
  }
}

Input Schema

NameRequiredDescriptionDefault
pincodeYes6-digit Indian pincode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.8/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 burden. It explains the output fields (district, city, state) but does not disclose behavioral traits such as read-only nature, authentication needs, rate limits, or potential errors. The description adds some context beyond the schema but lacks depth.

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, front-loaded with the action and input, and includes a brief summary of output. No unnecessary words or repetition.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides enough context: what the tool does and what it returns. It is complete for the purpose, but could mention error handling or format expectations.

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% for the single parameter 'pincode', so baseline is 3. The description repeats that it is a 6-digit Indian pincode, adding value by mentioning the output fields, but does not add new meaning for the parameter itself.

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 explicitly states the tool validates an Indian 6-digit pincode and returns district, city, and state. It uses a specific verb 'validate' and clearly distinguishes from sibling tools that deal with geocoding, address search, or mapping.

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 pincode validation but does not provide explicit guidance on when to use it versus alternatives (e.g., geocode or address_analytics). No when-not-to-use or context for exclusions 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