Skip to main content
Glama

Find post office

find-post-office
Read-onlyIdempotent

Finds Sri Lanka Post offices and postal codes. Search by post office name, 5-digit post code, short (tele) code, or a village or town name. Returns the post code, type, grade, whether it delivers, its division, phone numbers and, for a sub post office, the controlling post office. If no office matches the name, villages matching it are returned with the post offices serving their 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": {
      "query": "<query>"
    },
    "name": "find-post-office"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPost office name ("Kandy"), post code ("20000"), short code, or village/town name ("Peradeniya").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuinely non-obvious traits: which fields come back (post code, type, grade, delivery flag, division, phones, controlling post office) and the important fallback where unmatched names return villages with their serving offices. It does not say whether matching is exact or fuzzy, nor whether results are capped.

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?

Three tight sentences with no filler: purpose first, accepted inputs second, return shape and fallback last. Every clause carries information an agent would otherwise have to discover by trial.

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?

There is no output schema, so the description correctly takes on the job of naming the returned fields and describing the alternate village-response branch. For a single-parameter read tool, nothing needed to call it correctly is missing.

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% and the single parameter is described with the same examples the description repeats, so little new meaning is added. The only marginal gain is confirming the 5-digit post code format and short (tele) code as valid inputs.

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 (finds) plus a precisely scoped resource (Sri Lanka Post offices and postal codes), then enumerates the four accepted lookup keys. It is unmistakably distinct from the calculator/checker siblings, which handle fees, postage, and prohibited articles.

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

Usage Guidelines4/5

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

Clearly frames the input modes an agent can use — office name, 5-digit post code, short code, or village/town name — and explains the fallback path when a name doesn't match. It stops short of stating exclusions or naming an alternative tool, but none of the siblings overlaps, so the gap is minor.

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