Skip to main content
Glama
Sign In

tollbooth

by io.github.huwhitememes
OverviewDiscussionsAdmin

postal_code_lookup

City, state, geo for postal/zip codes (60+ countries).

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": {
      "country": "<country>",
      "postal_code": "<postal_code>"
    },
    "name": "postal_code_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes
postal_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It mentions returning city, state, and geo info but does not specify whether the operation is read-only, any authentication needs, rate limits, data freshness, or error handling. The term 'geo' is ambiguous.

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?

The description is a single concise sentence of 10 words, front-loading the essential purpose. It is efficient but potentially oversimplified, missing details that could improve clarity.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple lookup task and lack of output schema, the description is incomplete. It does not describe the return format, what 'geo' includes (e.g., coordinates, timezone), supported countries, or error behavior. The schema is also under-described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the description does not compensate. It mentions 'postal/zip codes' and '60+ countries' but fails to clarify expected formats (e.g., ISO country codes, postal code format) or provide examples. The agent must infer parameter meaning from the name alone.

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?

The description clearly states the tool's purpose: returning city, state, and geographic information for postal/zip codes, with coverage of 60+ countries. The verb 'lookup' is implied by the name and description, making it specific and distinguishable from sibling tools like ip_geolocation or geo_pulse.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor are there any exclusions or prerequisites. The description only states what the tool does, leaving the agent to infer usage context.

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

All tollbooth 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