Skip to main content
Glama

textokit_comparar_textos

Compare texts literally. 0.001 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": {
      "original": "<original>",
      "entrega": "<entrega>"
    },
    "name": "textokit_comparar_textos"
  }
}

Input Schema

NameRequiredDescriptionDefault
entregaYesString to compare against the original; at most 20000 UTF-16…
originalYesOriginal string; at most 20000 UTF-16 code units.
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 / entrega / description
      Previous value: -"String to compare against the original; at most 20000 UTF-16 code units. Keep the JSON key entrega."New value: +"String to compare against the original; at most 20000 UTF-16…"
    • 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."
  3. First observed

TDQS

B3.3/5.0
Behavior3/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 does disclose real behavioral traits: the price, the per-IP free quota, and the unusual fact that an unpaid call returns payment requirements rather than failing. It omits what the comparison actually returns (similarity score? diff? boolean?) and any limits or failure modes.

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?

Two dense sentences with the purpose front-loaded and no filler; the pricing and sample pointer are appended compactly. Slightly telegraphic jargon (x402, Base) but every clause carries information.

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

Completeness2/5

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

There is no output schema, so the description must convey the return value, and it does not: an agent cannot tell whether it receives a similarity score, a diff, or a boolean. Payment mechanics are covered well, but the core result shape of a 2-required-parameter comparison tool 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 coverage is 100%, with both required strings and the legacy payment_signature documented in the schema, so baseline is 3. 'Literally' hints at the comparison mode but the description does not explain original vs. entrega relationship or the preferred _meta payment channel beyond what the schema states.

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 ('Compare texts literally'), which is unambiguous and matches the tool name. It does not need to differentiate from siblings since none of them perform text comparison, but it also never clarifies scope (character-level vs. semantic, which languages).

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 description explains the payment flow (free 10 calls/day per IP, unpaid calls return x402 requirements) and points to textokit_sample for a free sample, which does route the agent. However, it gives no guidance on when comparing is appropriate, and no prerequisites for the paid path beyond the payment mention.

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.