Skip to main content
Glama

markdown

Convert a public web page into clean, agent-readable text by stripping scripts, styles, and navigation, and return the page title.

Instructions

Fetch a public web page and return clean Markdown (scripts/styles/nav stripped) plus title. Max 2 MB, 15 s timeout, public IPs only. Costs 0.002 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL of a public page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the whole burden and does well: it discloses content stripping, the 2 MB cap, the 15 s timeout, the public-IP restriction, the per-call price on Base, and the 402 failure mode when no payment key is present. It stops short of redirect, robots, caching, or rate-limit behavior, which are the remaining unknowns for a fetch tool.

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?

Three tight sentences: capability first, then hard limits, then cost and the failure mode. Every clause carries operational information an agent needs before calling.

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 tool with no output schema, the description covers the return shape (Markdown + title), limits, cost, and the 402 path, which is enough to invoke it correctly. It could say more about error modes other than the payment challenge.

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% for the single `url` parameter, so the baseline is 3. The description adds only the 'public IPs only' reachability constraint beyond the schema's 'http(s) URL of a public page' wording.

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 and resource ('Fetch a public web page') plus the exact transformation applied ('return clean Markdown, scripts/styles/nav stripped, plus title'). No sibling in the catalog is a generic page fetcher, so the function is unmistakable.

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?

Usage is implied by 'public web page' and 'public IPs only', and the payment-key prerequisite is spelled out. However, there is no explicit when-to-use framing or exclusion clause telling an agent when to prefer this over the structured-data sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.