comparador-luz-gas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| comparar_ofertasA | Consulta el comparador oficial de la CNMC y devuelve las ofertas de luz y/o gas, de la más barata a la más cara, con un análisis a varios años (rotar de oferta, permanencias, fijo vs. tramos). Luz: |
| leer_factura_qrA | Interpreta el texto ya decodificado del QR de una factura de luz y devuelve sus datos. |
| leer_factura_archivoA | Busca el QR del comparador en una factura de luz del disco del servidor y devuelve los mismos datos que |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
comparar_ofertas is clearly the action tool, while the two leer_factura_* tools are split by input source (QR text vs. file path) and the descriptions explicitly state which to use in each case. The two read tools share the same output purpose, so there is slight conceptual overlap, but the input distinction is documented well enough to avoid misselection.
All three names follow a consistent Spanish verb_noun snake_case pattern (comparar_ofertas, leer_factura_qr, leer_factura_archivo). The two leer_factura_* variants differ only by a meaningful suffix, so the convention is predictable throughout.
Three tools is on the lean side but fits the narrow scope of comparing offers and reading bill QR data. Each tool earns its place; the set is not padded, though it leaves little room for adjacent needs like gas bill parsing.
The core lifecycle is covered: compare light/gas offers, extract QR data from text, and extract it from a file. Minor gaps remain (e.g., no gas-bill QR reading, only electricity), but these are edge cases an agent can work around since comparison also accepts explicit cp/consumo arguments.