Skip to main content
Glama

Lookup: India PIN codes and districts, public holidays

India PIN code to post offices, district and state

lookup_pin
Read-onlyIdempotent

Look up an Indian six-digit PIN code: the post offices that use it (with India Post taluk), the state, and the district (the current district from the Local Government Directory where it can be matched safely by Census 2011 code, otherwise India Post's own label, which says which). Source: India Post office list via GeoNames (CC BY 4.0) and the Local Government Directory (GODL). Post offices change: it is a snapshot.

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

Input Schema

NameRequiredDescriptionDefault
pinYesSix-digit PIN code, e.g. "110001".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description then adds real value beyond them: data provenance (GeoNames/India Post, GODL), the conditional district-resolution rule with an explicit fallback labeling, and the staleness caveat that results are a snapshot. What it does not say is how an invalid or unmatched PIN is reported.

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?

The purpose and return values are front-loaded and every sentence carries information. The district clause is a deeply nested parenthetical that takes effort to parse, but nothing is redundant filler.

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?

With no output schema, the description correctly takes on the burden of describing return contents, provenance, and freshness — all present. The remaining gap is failure behavior for malformed or unrecognized PINs, which matters for a one-parameter lookup.

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% and the single 'pin' parameter is already documented with a six-digit example, so the description adds no format or validation detail beyond it. This is the expected baseline when the schema does the work.

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 opens with a specific verb and resource ('Look up an Indian six-digit PIN code') and immediately enumerates the returned fields: post offices with taluk, state, and district. An agent knows exactly what this tool answers without consulting the schema.

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?

Usage is only implied by the input shape: you use it when you already hold a PIN code. There is no explicit statement of when to prefer it over lookup_place or any exclusion for place-name queries, so the agent must infer the routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources