Skip to main content
Glama

AutoPay

fetch

Fetch one public web page and return clean Markdown ($0.01, synchronous, charged only on success). Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
linksNo
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 disclose cost ($0.01), synchronous execution, success-only billing, and two payment paths (X-PAYMENT x402 USDC on Base or prepaid API key). It leaves out rate limits, page-size limits, redirect/JS-rendering behavior, and error modes, which matter for an unannotated paid network call.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and output, followed by cost and payment mechanics – no filler or repetition.

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?

Covers the core facts an agent needs to call it: what it returns, that it is synchronous, that it costs money and how to pay. The missing piece is any explanation of the optional 'links' and 'max_chars' parameters, which is a real gap given 0% schema coverage.

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 0% across three parameters, and the description never explains what 'links' or 'max_chars' do or what format 'url' must take. It only implies the resource is a single public page, so the meaning of two of three parameters is undocumented anywhere.

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 (fetch) and resource (one public web page) plus the return shape (clean Markdown), which cleanly separates it from search/research/verify siblings that imply multi-result or agentic behavior.

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 scoping words 'one' and 'public' implicitly tell the agent this is single-page, unauthenticated fetching, but there is no explicit when-to-use or when-not guidance relative to search or research.

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