Skip to main content
Glama

scrape_markdown

PAID $0.001 USDC (x402, Base): URL to clean markdown. Over MCP this returns payment requirements; settle by calling POST /v1/scrape/markdown with x402 payment headers.

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 discloses the most important non-obvious behavior: this is a paid tool ($0.001 USDC), and the MCP call does not return markdown directly but payment requirements that must be settled via an HTTP POST. It omits details like failure/refund behavior, but the critical payment handshake is explicit.

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 dense sentence with the cost and payment caveat front-loaded. Every clause carries operational information; only the settlement path could be slightly clearer.

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?

For a one-parameter paid scraping tool with no output schema, the description covers the essential gotcha (payment requirements over MCP) and the settlement path. Return-value shape is implied by 'clean markdown', which is sufficient here.

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?

The single parameter is undocumented in the schema (0% description coverage). The description implies the url is the page to scrape into markdown, which gives the parameter meaning, but adds no format or validation detail beyond the schema's uri type.

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 resource and outcome: a URL converted to clean markdown, plus the payment model. It is distinguishable from siblings like check_url or extract_structured, though it never names or contrasts them.

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?

Provides operational guidance on how to complete the call (MCP returns payment requirements; settle via POST /v1/scrape/markdown with x402 headers). It does not say when to choose this over extract_structured or check_url, so selection guidance is only implied.

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