Skip to main content
Glama

textokit_source_bounded_summary

Summarize text with verified quotes (evidence-bound summary). 0.002 USDC per call (x402, Base), first 10 calls/day per IP free; 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": {
      "text": "<text>"
    },
    "name": "textokit_source_bounded_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to summarize; 1–4000 characters. Do not submit secrets…
languageNoOptional summary language: es or en. Defaults to es.
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. Changed2 schema fields changed
    • 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 / text / description
      Previous value: -"Text to summarize; 1–4000 characters. Do not submit secrets or sensitive data."New value: +"Text to summarize; 1–4000 characters. Do not submit secrets…"
  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 does well: it discloses the billing model, the free-tier limit (10 calls/day per IP), and the notable failure mode that an unpaid call returns x402 payment requirements rather than an error. It omits what the response looks like and whether calls are retried/charged on failure, which keeps it short of a 5.

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 compact sentences, front-loaded with the core capability, then pricing, then the sample pointer. No filler, and every clause carries information an agent needs before calling a paid tool.

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 3-param paid tool with no annotations and no output schema, the description covers capability, cost, quota, and payment-failure behavior. The remaining gap is the shape of the 'verified quotes' output, which an agent must discover empirically, but nothing essential for a correct invocation is missing.

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 the schema already documents text length bounds, the es/en language enum with its default, and the payment_signature payload format. The description adds only indirect payment context via the x402 note and does not clarify parameter behavior 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?

States a specific verb and resource ('Summarize text') and adds a distinguishing qualifier ('with verified quotes / evidence-bound summary') that separates it from the translate and compare siblings. It also names textokit_sample as the free alternative, though it never explicitly contrasts with textokit_comparar_textos or textokit_translate_es, which are the closest functional neighbors.

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?

Gives concrete operating context: cost per call, a free daily quota per IP, what happens on an unpaid call, and where to get a free sample. That is real routing guidance an agent needs before invoking a paid endpoint. It stops short of stating when-not to use it (e.g. for non-evidence or long-form text) or pointing to textokit_how_to_pay for the payment flow.

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.