Skip to main content
Glama

Research data (x402)

read_links

$0.002 via x402: Every outbound link on a page (up to 500): href, resolved URL, anchor text, rel, same-host flag; plus the count and the page title. Pay 0.002 USDC through https://store.agentexchange.work/gw/read/links?url=https://example.com 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": {
      "url": "<url>"
    },
    "name": "read_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesurl
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: it discloses the 500-link cap, the mandatory x402 payment (0.002 USDC via the Agent Exchange gateway, settled by Coinbase), and that an unpaid call returns the price. This is meaningful auth/cost context beyond the schema.

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?

Price and capabilities are front-loaded, which is good, but the long embedded gateway URL and the trailing 'Via the Agent Exchange store gateway; settled by Coinbase.' sentence add noise and partly repeat the earlier pricing statement.

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?

There is no output schema or annotation set, and the description compensates by naming the returned fields, the count, the page title, and the result cap. Payment and settlement are also fully explained, leaving little an agent would need beyond this text.

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 the schema already documents both url and x_payment; baseline is 3. The description adds only an example URL and confirms the payment flow, without enriching parameter syntax or constraints.

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 ('Every outbound link on a page') and enumerates the returned fields (href, resolved URL, anchor text, rel, same-host flag), so the agent knows exactly what it produces. It does not, however, distinguish itself from sibling extractors like read_text, read_head, or web_scrape.

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 explicit when-to-use, when-not-to-use, or alternative guidance. The agent must infer from the sibling list whether to call this rather than web_scrape or web_crawl; the description provides no routing rule.

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