Skip to main content
Glama

Agent Exchange store

ip_asn

$0.002 via x402: An autonomous system by number: holder name, whether it is announced, the number of announced prefixes (v4 and v6), and up to 20 prefixes. Pay 0.002 USDC through https://store.agentexchange.work/gw/ip/asn?as=13335 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": {
      "as": "<as>"
    },
    "name": "ip_asn"
  }
}

Input Schema

NameRequiredDescriptionDefault
asYesAS number, with or without the AS prefix
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.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the transactional side: it discloses the exact cost ($0.002 USDC), the x402 payment protocol, Coinbase settlement, and the gateway endpoint. It omits rate limits and error behavior, but the payment/settlement disclosure is substantial and unusual.

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?

The price is front-loaded, which is good, but the cost is stated twice ('$0.002 via x402' and 'Pay 0.002 USDC'), and the long inline URL and gateway/settlement tail add clutter. The field list is useful but the sentence is dense and slightly redundant.

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?

No output schema exists, so the description correctly specifies the return payload (holder, announced status, prefix counts, up to 20 prefixes). Combined with the payment disclosure, an agent has enough to call it and anticipate the response; only rate-limit and failure semantics are 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%, so both parameters are already documented in the schema ('AS number, with or without the AS prefix' and the x402 payment payload). The description adds only an example value (?as=13335) and restates the payment flow, so baseline 3 is 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?

The description names a specific resource (an autonomous system by number) and enumerates the returned fields: holder name, announced status, v4/v6 prefix counts, and up to 20 prefixes. This clearly distinguishes it from generic lookups like ip_lookup or ip_block. It stops short of a crisp leading verb ('look up'), but the scope is unmistakable.

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 use this tool versus the many sibling lookups (ip_lookup, ip_block, verify_dns). The only contextual guidance is payment mechanics, which describes how to invoke, not when this is the right tool. An agent must infer its niche from the name alone.

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