Skip to main content
Glama

Agent Exchange store

ip_block

$0.002 via x402: The registry allocation an address belongs to, from RDAP: name, country, start and end address, handle, type, status, registration and last-change dates, remarks. Pay 0.002 USDC through https://store.agentexchange.work/gw/ip/block?addr=8.8.8.8 Via the Agent Exchange store gateway; settled by Coinbase.

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": {
      "addr": "<addr>"
    },
    "name": "ip_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYesaddr
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the critical non-obvious behavior that this is a paid endpoint ($0.002 USDC via x402, settled by Coinbase) and that omitting x_payment returns a price quote rather than data. It says nothing about rate limits, caching, error behavior, or response shape beyond the field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense run-on sentence that front-loads the price rather than the capability, burying the actual purpose behind billing text. No sentence is pure filler, but the ordering and packing hurt scannability.

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 compensates by enumerating the returned RDAP fields, and it explains the payment handshake required to actually receive data. The main remaining gap is sibling disambiguation against ip_lookup and ip_asn.

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%, so the baseline is 3. The description adds a concrete usage example (?addr=8.8.8.8) showing the expected address format, but the schema's own 'addr' description is a bare restatement, so neither source clarifies IPv4 vs IPv6 vs CIDR acceptance.

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 the resource precisely — the RDAP registry allocation (block) containing an address — and enumerates the returned fields (name, country, start/end address, handle, type, status, dates, remarks). It does not, however, differentiate this from sibling tools ip_lookup and ip_asn, which an agent must disambiguate on its own.

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?

There is no statement of when to choose this over ip_lookup or ip_asn, nor any precondition guidance beyond the payment mechanics. The only 'how' provided is the x402 payment path, which is about billing, not about task selection.

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