Skip to main content
Glama

textokit_cartas_ar

Formal letter in Argentine Spanish. 0.005 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": {
      "remitente": "<remitente>",
      "destinatario": "<destinatario>",
      "lugarYFecha": "<lugarYFecha>",
      "asunto": "<asunto>",
      "hechos": "<hechos>",
      "solicitud": "<solicitud>"
    },
    "name": "textokit_cartas_ar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNoLetter type: reclamo, intimacion or solicitud. Defaults to…
asuntoYesSubject to include in the reference line of the letter
hechosYesSupplied facts for the body, ordered chronologically when…
plazoDiasNoOptional requested response period in days, from 1 to 60.…
remitenteYesName or identification to include in the signature
solicitudYesRequested action and conditions supplied by the buyer
lugarYFechaYesPlace and date supplied by the buyer
destinatarioYesRecipient person or organization
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 / hechos / description
      Previous value: -"Supplied facts for the body, ordered chronologically when the information permits"New value: +"Supplied facts for the body, ordered chronologically when…"
    • 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 / plazoDias / description
      Previous value: -"Optional requested response period in days, from 1 to 60. Does not determine a legal deadline or a due date."New value: +"Optional requested response period in days, from 1 to 60.…"
    • changedInput schema / properties / tipo / description
      Previous value: -"Letter type: reclamo, intimacion or solicitud. Defaults to reclamo when omitted. Does not determine legal effects."New value: +"Letter type: reclamo, intimacion or solicitud. Defaults to…"
  3. First observed

TDQS

A3.6/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 behavioral burden and does well on the commercial side: it states the price, network, free daily quota per IP, and that an unpaid call returns x402 payment requirements. It does not describe the output format or what the generated letter looks like, which keeps it from 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?

The description is front-loaded with purpose and then covers pricing, quota, failure behavior, and the free sample in compact form. Every sentence carries operational information and there is no filler.

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 9-parameter generation tool with no annotations and no output schema, the description covers purpose, pricing, and payment mechanics well. It could say more about the returned letter format or structure, but the rich schema plus the payment details make it largely complete.

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 parameters are already well documented in the input schema. The description adds no parameter-specific meaning, such as how tipo interacts with plazoDias or what constitutes good hechos, so the baseline 3 is appropriate.

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 identifies the artifact and locale precisely: a formal letter in Argentine Spanish. It lacks an explicit verb like 'generate' and does not distinguish itself from sibling tools such as textokit_normativa_ar or textokit_translate_es, but the resource is clear enough for an agent to infer the purpose.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use or when-not-to-use guidance. It mentions the free sample tool but only as a sampling option, not as a conditional alternative or a rule for choosing this tool over other siblings.

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.