Skip to main content
Glama

Check ZIP coverage

check_service_zip
Read-onlyIdempotent

Check whether Fold serves a given ZIP code. Returns service availability, the market name (LA/SF), and a list of pickup window options that can be passed to book_residential_pickup. book_residential_pickup only accepts ZIPs this tool reports as served.

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": {
      "zipCode": "<zipCode>"
    },
    "name": "check_service_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipCodeYes5-digit US ZIP code, e.g. "90210" or "94103". ZIP+4 and full addresses are accepted; the 5-digit ZIP is extracted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / zipCode / description
      Previous value: -"5-digit US ZIP code, e.g. \"90210\" or \"94103\"."New value: +"5-digit US ZIP code, e.g. \"90210\" or \"94103\". ZIP+4 and full addresses are accepted; the 5-digit ZIP is extracted."
  2. First observed

TDQS

A4.5/5.0
Behavior4/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 genuine value by disclosing the return shape and the hard dependency relationship with the booking tool. It stops short of noting latency, caching, or what 'not served' looks like in the response, which keeps it off a 5.

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 short sentences, front-loaded with the core question, followed by the return values, then the critical downstream constraint. No filler and nothing buried.

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?

No output schema exists, yet the description still tells the agent what is returned (availability, market, pickup windows). For a single-param read tool with full annotation coverage, nothing an agent needs to invoke 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 zipCode parameter already documents the 5-digit format plus ZIP+4/address extraction behavior. The description adds no parameter-level detail beyond what the schema states, so the baseline 3 applies.

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 and resource ('Check whether Fold serves a given ZIP code') and immediately enumerates what comes back: availability, market name, pickup window options. An agent can distinguish it from coverage-adjacent siblings like get_service_info or list_campuses without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the downstream tool (book_residential_pickup) and the gating condition: 'book_residential_pickup only accepts ZIPs this tool reports as served.' That is a concrete when-to-use rule with the alternative stated, leaving nothing to inference.

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