Skip to main content
Glama

textokit_url_text

Texto legible de una página pública. 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_url_text"
  }
}

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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well for the key economic traits: price per call, what happens on an unpaid call (returns x402 payment requirements), and a free alternative. It omits rate limits and failure modes, but adds substantial context beyond the schema.

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 sentences: the first front-loads the purpose, the second handles payment and the free sample. No sentence restates the name or wastes space.

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?

Given no output schema and no annotations, the description supplies the essential payment and sample-routing context. It still leaves the return shape slightly vague ('texto legible') and says nothing about error behavior, but the schema covers the output format and length controls.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description adds no parameter-specific detail beyond what the schema provides, which is the baseline case for high coverage.

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 public page) and the output (readable text), so the basic purpose is clear. However, it lacks an explicit verb and does not differentiate from sibling tools such as textokit_web_read or textokit_source_bounded_summary.

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?

Points to a free sample (textokit_sample) and discloses the paid path, which implies usage. But it does not say when to choose this over textokit_web_read or other text-extraction siblings, nor any exclusions.

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.