Skip to main content
Glama

BRAINIAC Web & Page Intelligence

Convert URL to Markdown

web-intelligence_url-to-markdown
Read-onlyIdempotent

Fetch one public webpage and convert its readable HTML into Markdown. Scripts are not run, and missing text is not filled in. Price $0.04 USDC. POST /api/v1/web-intelligence/url-to-markdown. An unpaid call returns the x402 payment terms and does not run.

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-intelligence_url-to-markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesurl, string, length 8 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
finalUrlNofinalUrl. String.
markdownNomarkdown. String.
warningsNowarnings. Array.
httpStatusNohttpStatus. Number.
contentHashNocontentHash. String.
contentTypeNocontentType. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
requestedUrlNorequestedUrl. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, yet the description adds real substance on top of that: JavaScript is not executed, missing text is not synthesized, the call costs $0.04 USDC, and an unpaid call returns x402 payment terms without running. That is exactly the kind of pricing, auth and execution-model context an agent cannot get from structured fields.

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?

Four short sentences, front-loaded with the action, then execution limits, then price and payment behavior. No filler. The endpoint path is arguably redundant for an agent but it is a single clause and supports the x402 payment note that follows it.

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

Completeness5/5

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

A output schema exists, so return-shape explanation is not required, and the description covers the remaining gaps an agent would care about: execution model, missing-content policy, cost, and the unpaid-call failure mode. Nothing needed to invoke it correctly is absent.

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 and schema description coverage is 100%, so the schema already documents the URL and its constraints. The description's 'one public webpage' reinforces the single-URL model but adds no syntax, normalization or encoding detail beyond the schema. 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 verb and resource: 'Fetch one public webpage and convert its readable HTML into Markdown.' The scope word 'one' and the phrase 'readable HTML' distinguish it from bulk crawlers and structured extractors. It does not name a sibling tool, so it falls just short of a 5.

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 implicit: the tool is for a single public page, and the line 'Scripts are not run, and missing text is not filled in' quietly tells the agent not to use it for JavaScript-rendered or partial content. There is no explicit when-to-use or when-not-to-use guidance and no mention of the structured-extract siblings that would be the alternative for typed data.

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