Skip to main content
Glama
Sign In

2extract

by com.2extract
OverviewDiscussionsAdmin

Search Geo ISP

searchGeoISP
Read-only

Search the ISP catalog for mobile ISP targeting (mobile proxies only). Always resolve the code through this tool — never accept a real-world ASN number as a substitute. Returns each carrier's name and catalog code, the value for buildConnectionString's isp. Response fields: docs://geo/searchGeoISP.

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": "searchGeoISP"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 100, max 500
searchNoISP name substring search, minimum 3 characters, e.g. 'AT&T'

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.2/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 the non-obvious behavioral constraint that only mobile ISP entries exist in the catalog and that ASN numbers are not interchangeable with catalog codes. It also sketches the response shape (carrier name plus catalog code) and defers the field list to a docs URI.

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 tight sentences: purpose and scope first, the hard constraint second, return values and doc pointer last. No filler, and the most decision-relevant constraint is front-loaded.

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 output schema, the description still tells the agent what comes back (carrier name and catalog code) and where to find the full field list via docs://geo/searchGeoISP. Complete enough to call correctly, though an agent must follow an external reference for exact response fields.

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%, with both `limit` and `search` documented including defaults, max, and a minimum-length example. The description adds no syntax or format detail beyond 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.

Purpose5/5

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

States a specific verb+resource ('Search the ISP catalog') and immediately narrows scope to 'mobile ISP targeting (mobile proxies only)', which separates it from the geo country/city/region/zip siblings. It also names the downstream consumer, buildConnectionString's isp parameter, so the agent knows exactly what the result is for.

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 a hard usage rule: 'Always resolve the code through this tool — never accept a real-world ASN number as a substitute,' which is explicit when-to-use guidance tied to the buildConnectionString workflow. It stops short of describing the browse-vs-search paths (calling with only `limit` to enumerate vs. using `search`), so it is not fully exhaustive.

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