Skip to main content
Glama

Page markdown

page_markdown
Read-onlyIdempotent

A web page as clean Markdown for an LLM, rendered in a real browser (JavaScript runs); a failed render is not charged. $0.002 per call over x402.

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

Input Schema

NameRequiredDescriptionDefault
urlYesthe http(s) page
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, and the description adds genuinely new operational context: a per-call charge of $0.002 over x402 and the guarantee that a failed render is not charged. It stops short of describing output size, truncation, or what happens on non-2xx pages.

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 tight sentences with the core capability front-loaded and the commercial terms appended second; no filler and nothing repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Pricing and render-failure behavior are covered, but with no output schema the description should say something about the shape of the returned Markdown (full page vs. main content, size limits). That is a meaningful gap for a fetch-and-convert tool.

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 url and payment are fully documented in the schema, including the note that the payment payload completes the purchase in-call. The description adds no parameter detail beyond the schema, which meets the baseline for high-coverage schemas.

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 the resource (a web page) and the output form (clean Markdown for an LLM), plus the key differentiator that rendering happens in a real browser with JavaScript executed. That distinguishes it in spirit from static-conversion siblings like html_to_markdown, though no sibling is named explicitly.

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 'JavaScript runs' clause implies when this tool is preferable (JS-heavy or dynamically rendered pages), and the pricing clause implies a cost tradeoff, but there is no explicit when-to-use/when-not statement or named alternative.

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