Skip to main content
Glama

Lookup: India PIN codes and districts, public holidays

Indian place name to district

lookup_place
Read-onlyIdempotent

Which district is an Indian town or locality in? Returns matches with district, state, the basis (a town page with a Local Government Directory district, or India Post's label that the directory does not confirm) and a link to the page. About 19,000 towns and localities; old names such as Bangalore or Gurgaon resolve. Source: India Post via GeoNames (CC BY 4.0) and the Local Government Directory (GODL).

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

Input Schema

NameRequiredDescriptionDefault
nameYesPlace name, e.g. "Adoni".
stateNoOptional state name to narrow the match, e.g. "Andhra Pradesh".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the bar is lower, and the description still adds real value: it enumerates the returned fields (district, state, basis, link), explains what the 'basis' flag means, and discloses data provenance and licensing. It does not say what happens on zero matches or multiple ambiguous matches, which is the main remaining gap.

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 description is front-loaded with the core question, then moves to return shape, coverage, and provenance in a logical order. The parenthetical explaining 'basis' is dense but earns its place; nothing is redundant with the title.

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 carries the burden of explaining returns and does so by naming the fields. It covers scope, source, and resolution behaviour for a simple two-parameter lookup, though edge-case behaviour (no match, ambiguous match) is left unspecified.

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?

Schema coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds meaning beyond the schema by noting that historical names such as Bangalore and Gurgaon resolve, signalling alias/fuzzy matching on the name parameter that the schema does not convey.

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 opening question, "Which district is an Indian town or locality in?", states a specific input-to-output mapping (place name → district) that an agent can match to a user question immediately. It is clearly distinct from the pin-code sibling lookup_pin and from the holiday 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?

Scope is implied well (Indian towns and localities, ~19,000 places, old names like Bangalore or Gurgaon resolve), which tells the agent what inputs are valid. However, there is no explicit when-to-use statement, no when-not-to-use, and no mention of alternatives such as lookup_pin for pincode-based queries.

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