Read the QR code in a Spanish electricity bill PDF or image from local disk and return its data to compare energy offers. Requires the facturas extra and poppler-utils for PDFs.
Lee el QR de una factura de luz en PDF o imagen del disco local y devuelve sus datos. Necesita el extra facturas (y poppler-utils para PDFs).
| Name | Required | Description | Default |
|---|---|---|---|
| ruta | Yes | ruta al PDF o imagen de la factura |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds useful operational context beyond that: it operates on local disk files and requires the 'facturas' extra plus poppler-utils for PDF parsing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. The core action is front-loaded, followed by the dependency requirement.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool, the definition covers the input and key dependencies, and annotations cover the safety profile. It is slightly incomplete because it does not describe the returned invoice data in any detail and does not disambiguate from the sibling tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the single 'ruta' parameter is already documented as the path to the PDF or image. The description adds only the minor clarification that the file is on local disk, which does not materially extend the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: reads the QR from an electricity invoice PDF or image on the local disk and returns its data. The scope is clear, but it does not distinguish itself from sibling leer_factura_qr, which appears to cover a very similar capability.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a dependency prerequisite (needs the extra 'facturas' and poppler-utils for PDFs) but no when-to-use guidance or criteria for choosing this tool over leer_factura_qr or comparar_ofertas.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.