Skip to main content
Glama

zato crypto data

Web page to clean Markdown (GET): title, description, main content, absolute links - robots.txt respected

page_markdown
Read-only

Readable content of a public web page as clean Markdown (robots.txt respected). Price: $0.0015 USDC per call (x402, Base).

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
urlYespublic page URL
max_charsNooptional max characters (default 20000)

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?

Beyond the readOnlyHint/openWorldHint annotations, the description discloses two genuinely useful behaviors: robots.txt is respected (so some URLs will be refused) and each call costs $0.0015 USDC via x402 on Base. It stops short of describing truncation behavior or failure modes for non-public 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 short clauses, zero filler, with the core capability first and the pricing constraint second. Nothing could be removed without losing information.

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 two-parameter read-only extraction tool with no output schema, this is close to sufficient: cost, safety, and crawling etiquette are covered. The remaining gaps are truncation semantics for max_chars and the exact shape of the returned Markdown (title, description, absolute links), which appear only in the title.

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 max_chars are already documented with a default of 20000. The description only reinforces that the URL must be public; it adds no format, length, or truncation detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific resource and output shape: readable content of a public web page rendered as clean Markdown. It is instantly distinguishable from every sibling, which are wallet/crypto/check utilities, though that differentiation comes from context rather than the text itself.

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 only implied by the scope restriction 'public web page' and the price note; it never says when to pick this over fetching content another way, nor what to do when a page is paywalled or JavaScript-only.

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