Skip to main content
Glama

textokit_web_read

Web page to Markdown: read any public URL as clean text. 0.001 USDC per call (x402, Base); an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS page URL. Private addresses and pages requiring…
formatNoOutput format: plain text or simple Markdown. Defaults to…text
maxCharsNoMaximum returned text length in UTF-16 code units, from 1000…
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed4 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Output format: plain text or simple Markdown. Defaults to text."New value: +"Output format: plain text or simple Markdown. Defaults to…"
    • changedInput schema / properties / maxChars / description
      Previous value: -"Maximum returned text length in UTF-16 code units, from 1000 to 20000. Defaults to 10000."New value: +"Maximum returned text length in UTF-16 code units, from 1000…"
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
    • changedInput schema / properties / url / description
      Previous value: -"Public HTTPS page URL. Private addresses and pages requiring authentication are unsupported."New value: +"Public HTTPS page URL. Private addresses and pages requiring…"
  3. First observed

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 full burden, and it discloses the key behaviors: 0.001 USDC per call, x402 on Base, and that unpaid calls return payment requirements instead of erroring. It omits rate limits and any statement about restrictions (private addresses), though the schema covers the latter.

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, front-loaded with what it does, then pricing and failure behavior, then the free alternative. No wasted words.

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 4-parameter paid HTTP-fetch tool with full schema coverage and no output schema, the description covers the payment flow and the free path well. The one missing piece is how it differs from textokit_url_text, which matters for tool selection.

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 the schema already documents url, format, maxChars, and payment_signature. The description only echoes the Markdown format concept and adds no syntax or usage detail beyond the structured fields. 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?

States a specific verb and resource: reads a public URL and converts it to clean text or Markdown. It is clear what the tool returns. It does not, however, differentiate itself from the sibling textokit_url_text, which sounds functionally similar, leaving that ambiguity unresolved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the free alternative (textokit_sample) and the condition that makes it relevant, and states that an unpaid call returns payment requirements rather than failing. No guidance on when to prefer this over textokit_url_text, which is a real gap given the sibling list.

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.