Skip to main content
Glama

img_tools_qr_generate

[$x402 pago por llamada] Genera un código QR como SVG a partir de un texto.

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

Input Schema

NameRequiredDescriptionDefault
textYesTexto a codificar (1-2000 caracteres).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose two meaningful traits beyond the schema: the output is SVG and each call is paid via x402 (402 returned if no payment header). It says nothing about QR options (size, error correction) or failure modes for out-of-range text, leaving real gaps for a no-annotation tool.

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?

A single sentence with the payment caveat front-loaded in brackets and the action stated immediately. No waste, though the bracketed tag is slightly noisy.

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 two-parameter, fully documented tool with no output schema, the description supplies the return format (SVG) and payment behavior, which is what an agent needs. Only secondary details like QR size or error-correction defaults are 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%, including the 1-2000 character limit and the X-PAYMENT header semantics, so the schema already does the work. The description only restates that a text is the input, adding no semantics beyond structured data.

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 pair ('Genera un código QR como SVG a partir de un texto'), so the agent knows exactly what comes out. It does not name or contrast with the natural alternative, sibling img_tools_qr_decode, though the generate/decode split is self-evident from the verb.

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?

Usage is implied by the verb-resource pairing (give text, get a QR), and the bracketed note signals the pay-per-call constraint. There is no explicit when-to-use / when-not-to-use guidance or reference to the decode sibling.

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.

Resources