Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_asn

Read-onlyIdempotent

BGP routing intelligence: ASN, IP prefix, organization and country (0.0050 USDC / 1 credit).

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

Input Schema

NameRequiredDescriptionDefault
ipNoOptional IPv4/IPv6 address (defaults to 1.1.1.1).
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by disclosing the price (0.0050 USDC / 1 credit), but says nothing about what the payment_tx_hash flow does, whether a call fails without payment, or what sandbox mode returns.

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?

A single line that front-loads the data domain and its fields, with the cost appended last. Nothing is wasted, though the one-liner format leaves no room for the payment or default-address context the tool actually needs.

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

Completeness3/5

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

Because there is no output schema, the field enumeration (ASN, prefix, org, country) usefully describes the return payload. However, a paid tool with an unusual credential parameter (session pass, EIP-3009 payload, demo sandbox) needs more explanation of the payment path than a single price tag.

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 both the ip and payment_tx_hash semantics, including the default address and the accepted credential formats, are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 domain (BGP routing intelligence) and enumerates the returned fields: ASN, IP prefix, organization, country. That is enough for an agent to know this is an IP-to-ASN/routing lookup, but it draws no boundary against adjacent siblings such as grid402_dns or grid402_crypto.

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 when-to-use or when-not-to-use guidance, no mention of the sibling tools that handle DNS or domain work, and no note that the IP parameter defaults to 1.1.1.1 when omitted. The agent must infer the calling context entirely from the noun phrase.

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.