Skip to main content
Glama
Sign In

2extract

by com.2extract
OverviewDiscussionsAdmin

Search Geo ZIP Codes

searchGeoZips
Read-only

Search ZIP codes within a country, for use in proxy username params. Returns ZIP values to pass as buildConnectionString's zip; ZIP targeting cannot be combined with state or city. Response fields: docs://geo/searchGeoZips.

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_code": "<country_code>"
    },
    "name": "searchGeoZips"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 100, max 500
searchNoZIP substring search, minimum 3 characters, e.g. '123'
country_codeYesISO country code, e.g. 'US', 'DE'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results, default 100, max 200"New value: +"Max results, default 100, max 500"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value with the ZIP-vs-state/city exclusivity constraint and the downstream destination of the returned values. It does not state pagination/limit behavior, though the schema covers limit.

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?

Three short sentences, front-loaded with the purpose, then the downstream use, then the exclusivity constraint. Every sentence carries information; the docs pointer for response fields is compact rather than wasteful.

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?

There is no output schema, and the description compensates by naming where response fields are documented ('docs://geo/searchGeoZips') plus the key targeting constraint. For a 3-parameter read-only search with high schema coverage, nothing essential 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 description coverage is 100%, so country_code, search, and limit are already fully documented with examples and bounds. The description adds no per-parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 verb and resource ('Search ZIP codes within a country') and ties it to a concrete use case ('for use in proxy username params'). It implicitly distinguishes itself from siblings like searchGeoCities/searchGeoRegions via the 'ZIP targeting cannot be combined with state or city' note, but never names those siblings directly.

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 clear usage context: values feed buildConnectionString's zip and ZIP targeting is mutually exclusive with state/city targeting. That is an actionable when-to-use and when-not-to-combine rule. It stops short of explicitly routing the agent to searchGeoCities/searchGeoRegions for the alternative targeting modes.

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

All 2extract 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