Skip to main content
Glama

Agent Exchange store

read_head

$0.002 via x402: Only the head of a page, no body text: status, final URL after redirects, content type and length, server, last-modified, cache headers, title, meta description, canonical, robots meta, language, Open Graph and Twitter card fields. Pay 0.002 USDC through https://store.agentexchange.work/gw/read/head?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_head"
  }
}

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

A3.8/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 a paid, x402-metered operation, the exact $0.002 cost, the USDC settlement path, and via Coinbase. It does not discuss failure modes or rate limits, but the payment/return behavior is transparent.

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 front-loads the price, which is good, but the text is a dense run-on that repeats the cost ('$0.002' then '0.002 USDC') and the gateway reference twice, and embeds a literal example URL. Functional but not tight.

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 must specify return values, and it does so exhaustively via the field enumeration. Combined with the disclosed payment mechanics, an agent has enough to call it correctly; only failure/timeout behavior is unaddressed.

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 (url, x_payment) are already documented in the schema. The description adds little parameter-level meaning beyond implying the url target and the payment gate, 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 ('read... the head of a page') and then enumerates exactly what it returns (status, final URL, content type/length, server, headers, title, meta, OG/Twitter cards). The 'no body text' clause sharply distinguishes it from read_text and markdown_web_scraper siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Only the head of a page, no body text' phrase implies the right usage context (metadata inspection rather than content extraction), but no sibling is named and there is no explicit when-to-use/when-not guidance. Usage must be inferred from the scope statement.

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