Skip to main content
Glama

meskeIA MCP

by com.meskeia

calcular_gasto_energetico

Read-only

Calcula el consumo eléctrico mensual del hogar y la factura estimada. A partir de los electrodomésticos (potencia, horas de uso, días al mes) calcula los kWh totales y desglosa la factura con todos los conceptos: coste de energía, término de potencia, impuesto eléctrico (5.113%) e IVA (21%).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preciokWhNoPrecio del kWh en euros. Por defecto 0.15 €/kWh (mercado libre orientativo). PVPC media ~0.13 €/kWh.
electrodomesticosYesLista de electrodomésticos con su potencia y uso
potenciaContratadaKWNoPotencia contratada en kW. Habitual: 3.45, 4.6, 5.75, 6.9, 8.05 kW. Por defecto 4.6 kW.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, so the tool is read-only. The description adds context about the calculation breakdown (kWh total, concepts like impuesto eléctrico and IVA), which goes beyond the annotation. There is no contradiction.

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?

Two sentences, no fluff. First sentence states the primary purpose; second sentence details the calculation and output. Every word earns its place.

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?

The description covers the tool's purpose, inputs (implied), and output breakdown. While no output schema exists, the description sufficiently explains what the tool returns. Annotations confirm read-only behavior. Slight gap: exact output format is not specified, but acceptable for a calculator tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented. The description adds meaning by stating the bill includes specific concepts (coste de energía, término de potencia, impuesto eléctrico 5.113%, IVA 21%), which clarifies the output beyond what the schema covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates monthly household electricity consumption and estimated bill. The verb 'Calcula' and resource 'consumo eléctrico mensual' are specific. The tool is well-differentiated from siblings (many other calculators) by its focus on household energy billing.

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?

The description implies usage for household electricity billing but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or alternative tool references are provided, though the name and context make the purpose clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All meskeIA MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools are cleanly separated by domain and purpose, but a few close pairs exist: calcular_camara_lenta and calcular_regla_180_video both touch the 180° shutter rule, and calcular_pace_running and calcular_prediccion_running both produce race projections. The descriptions are detailed enough to resolve the ambiguity, but misselection is possible if they are not read carefully.

Naming Consistency5/5

All tool names follow a consistent Spanish verb_noun snake_case pattern, with calcular_ dominating and the other verbs (convertir_, consultar_, recomendar_, escalar_) used for genuinely different action types. There is no mixed casing or style inconsistency.

Tool Count2/5

42 tools is far above the 25+ threshold and the set spans many unrelated domains such as cooking, fitness, photography, vehicles, dates, and finance. While each individual calculator may be useful, the server is not well-scoped and would be much easier to navigate if split into domain-specific MCP servers.

Completeness3/5

Coverage inside each sub-domain is quite thorough, but there are notable gaps: calcular_kilometraje references calcular_irpf, calcular_cuota_autonomo, and comparar_autonomo_vs_sl, none of which exist in this server. These dangling cross-references can lead an agent to attempt calling unavailable tools.

Resources