Skip to main content
Glama
india-pincode-ifsc-mcp

india-pincode-ifsc-mcp

by Ankur1911

search_post_offices

Read-onlyIdempotent

Search Indian post offices by name to get PIN codes, office type, delivery status, district, and state. Use district and state to distinguish repeated place names.

Instructions

Find Indian post offices by name (locality, town or office name) and get each one's PIN code, type, delivery status, district and state. Names repeat across India (there are many 'Gandhi Nagar'), so check district and state. Use it to go from a place name to a PIN code; use lookup_pincodes to go from a PIN to its area.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPost office or locality name, at least 3 characters, e.g. 'Connaught Place'.
limitNoMaximum post offices returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the description's main added value is the data-quality caveat about duplicate names and the list of returned attributes. It does not discuss result ordering, truncation behavior when limit caps matches, or whether a no-match returns an empty list versus an error — gaps that matter for an open-world search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose, then the disambiguation caveat, then the sibling routing. No filler, though the return-field list could be trimmed since the schema already signals the resource.

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?

No output schema exists, so the description appropriately names the returned attributes, and the ambiguity warning covers the main failure mode of a name-based search. Only the pagination/limit semantics and empty-result behavior are left unaddressed.

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 coverage is 100%, so baseline is 3. The description slightly broadens 'name' beyond the schema wording (locality, town or office name) and warns that matches may be ambiguous, but it adds no detail on how limit interacts with ambiguous matches or how to page past the cap.

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?

States a specific verb and resource ('Find Indian post offices by name') and enumerates the return fields (PIN code, type, delivery status, district, state). It also explicitly separates itself from lookup_pincodes, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives bidirectional routing guidance: use this tool to go from place name to PIN, use lookup_pincodes to go from PIN to area. It also supplies a concrete when-to-be-careful rule ('Names repeat across India... so check district and state'), leaving nothing to inference.

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