Skip to main content
Glama
Sign In

Zip-Codes.com Location Intelligence: Spatial Analysis, Districts & 14+ Years of Demographics

by com.zip-codes
OverviewDiscussionsAdmin

ZIP Code facts

zip_facts
Read-onlyIdempotent

Statistics about US ZIP Codes and Canadian postal codes: how many exist, how they break down by type, delivery point and carrier route totals, per-state tables, and ranked lists such as the ZIP Codes with the most carrier routes. Every figure is generated from a stored query against the source data, with the date it was measured. Costs nothing and needs no key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zip_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: figures come from stored queries against source data, each carries a measurement date, and no key or cost is required. It does not describe result size or pagination, so the addition is useful but not rich.

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?

A single dense sentence that front-loads the subject and then enumerates what is available, with the provenance and cost caveats trailing. The enumeration is long but every clause adds information; no filler sentences.

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 parameters and no output schema, the description must convey what comes back, and it does so by listing the categories of figures and noting the measurement date accompanying each. What remains unstated is the shape of the response (e.g., grouping or formatting), which is a minor gap for a zero-argument facts tool.

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?

The tool takes zero parameters, so there are no semantics for the description to compensate for; baseline is 4. Schema coverage is 100% and the empty object schema is self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (US ZIP Codes and Canadian postal codes) and enumerates the categories of statistics returned: totals, type breakdowns, delivery point and carrier route counts, per-state tables, and ranked lists. It does not explicitly name how it differs from siblings like zip_lookup or quick_zip, but the aggregate-statistics framing implicitly separates it from per-record lookup 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?

Usage is only implied: an agent can infer this is for aggregate/reference facts rather than individual code lookups. There is no explicit 'use when' statement, no exclusions, and no routing to zip_lookup or quick_zip for single-code queries.

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

All Zip-Codes.com Location Intelligence: Spatial Analysis, Districts & 14+ Years of Demographics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources