Agent Tools

web_to_markdown

Convert a web page URL to clean Markdown for LLMs, research, RAG and summarization. Extracts main content without navigation or scripts. Returns title, status and LLM-ready markdown. Respects robots.txt. Price $0.0015 USDC per call via x402. Example output: {"url":"https://example.com/","status":200,"title":"Example Domain","characters":156,"markdown":"This domain is for use in documentation examples..."}

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public page URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description does real work: it states content extraction behavior (main content only, no nav/scripts), robots.txt compliance, and a per-call price of $0.0015 USDC via x402. It omits failure behavior, rate limits, and whether payment setup is a prerequisite, so the mutation/cost profile is only partly disclosed.

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?

The core purpose and behavior lead the sentence, and the example output is compact and informative. The pricing and example JSON add length, but both earn their place given there is no output schema.

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 fetch tool with no output schema, the description covers what the tool returns (title, status, markdown) and even shows a concrete sample response, plus the payment and robots.txt constraints. Missing only error-mode and rate-limit details, which are minor at this complexity.

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?

There is a single parameter with 100% schema description coverage ("Public page URL"), so the schema already carries the meaning. The description adds only the implicit constraint that the URL must be publicly reachable and robots-permitted, which is a modest addition beyond structured data.

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?

"Convert a web page URL to clean Markdown" gives a specific verb and resource, followed by the intended consumers (LLMs, research, RAG, summarization). It does not name or contrast with sibling tools like web_read_full or safe_web_read, so an agent must infer which of the reading tools to pick.

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 use cases (research, RAG, summarization) imply when the tool is appropriate, and "extracts main content without navigation or scripts" hints at its niche versus raw fetching. But there is no explicit when-to-use/when-not guidance and no reference to the available alternatives despite several sibling web-reading tools.

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

All Agent Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?