Skip to main content
Glama

Glazed Data Rent Limits

What data covers a ZIP

coverage
Read-only

Which data layers (federal, tax-credit, local agency) exist for a US ZIP code. Free, no key needed.

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_code": "<zip_code>"
    },
    "name": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
zip_codeYes5-digit US ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false) and closed-world behavior, so the bar is lower. The description adds genuinely new context — 'Free, no key needed' tells the agent no auth setup is required — and enumerates the layer categories, but says nothing about what happens for a ZIP with no coverage or how results are returned.

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 short sentences, front-loaded with the core question and followed by the access constraint. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of indicating what comes back; 'which data layers exist' hints at a list but does not say whether it is layer names, identifiers, or availability flags — information an agent needs to chain into sibling tools. For a simple single-parameter lookup it is nearly adequate, but that return-value gap is real.

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% with a regex pattern and a description for zip_code, so the schema already fully specifies the only parameter. The description adds nothing beyond 'US ZIP code', which restates the schema, so the baseline 3 applies.

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?

The description names a specific resource (data layers) and scope (federal, tax-credit, local agency) for a US ZIP code, so an agent can tell this is a coverage/discovery lookup rather than a data-returning tool like the sibling rent or income-limit endpoints. It lacks an explicit statement that it is a meta/discovery call, which keeps it short of a 5.

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 implied rather than stated: enumerating layer types suggests this is a first-step check before calling a specific dataset tool, but the description never says when to use it, when not to, or which sibling to call next. No alternatives are named.

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