Skip to main content
Glama

CoinVet

US ZIP code to city, state, coordinates and time zone

us_zip_lookup
Read-onlyIdempotent

Look up a US ZIP code: city/place names, state, latitude/longitude and the state's primary IANA time zone. Useful for checkout/address sanity checks and shipping estimates.

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

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered; the description adds the meaningful nuance that the returned zone is the state's primary IANA zone rather than a ZIP-precise one, heading off misuse. It does not say how a nonexistent or malformed ZIP is handled, which is the remaining behavioral gap.

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?

Two sentences, zero filler, with the resource and returned fields front-loaded ahead of the use-case note. Nothing repeats the tool title verbatim without adding information.

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 is the only source describing return values, and it does so adequately by listing all four field groups plus the time-zone caveat. Error behavior for invalid ZIPs is the only omission, and the single-parameter surface keeps this tool simple.

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 "zip" property already documents the 5-digit US format, so the description adds no format, normalization, or edge-case detail beyond it. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 ("Look up") and resource ("a US ZIP code") and enumerates the returned fields: city/place names, state, lat/long, and IANA time zone. This is plainly distinguishable from the sibling tools, which are all validators or crypto-price lookups.

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?

Gives concrete usage context ("checkout/address sanity checks and shipping estimates"), which tells an agent the intended call site. It stops short of explicit when-not guidance or naming an alternative for non-US postal codes, which is the only gap.

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