Skip to main content
Glama

img_tools_qr_decode

[$x402 pago por llamada] Decodifica todos los códigos QR presentes en una imagen (puede haber más de uno).

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": {
      "file_base64": "<file_base64>"
    },
    "name": "img_tools_qr_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
file_base64YesContenido del archivo codificado en base64 (o data URL). Se convierte a multipart/form-data internamente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full disclosure burden. It does convey two useful behavioral traits: the call is paid per invocation ('pago por llamada') and it returns all QR codes found rather than one. It omits error behavior (no QR detected, malformed base64) and the 402 flow, although the schema's x_payment field documents the latter.

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?

A single front-loaded sentence with no waste; the cost marker and the multi-code scope are both stated up front.

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 simple two-parameter tool with fully documented schema and no output schema, the description adequately conveys what comes back (all QR codes found). Minor gap: it doesn't say what happens when no code is present or what limits apply to image input.

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%, so both file_base64 and x_payment are already fully described in the schema, establishing the baseline of 3. The description adds no param-level detail such as accepted image formats or base64/data-URL specifics.

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 ('Decodifica') and resource ('códigos QR presentes en una imagen'), and the parenthetical clarifies the multi-code scope, which cleanly separates it from the sibling img_tools_qr_generate. It does not explicitly name the sibling, but the decode/generate distinction is unambiguous.

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 only implied by the verb and the note that an image may contain more than one QR code. There is no explicit when-to-use vs when-not guidance or reference to alternatives such as docs_tools_ocr or img_tools_qr_generate.

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