Skip to main content
Glama

Link Energy México — Catálogo Público

calculate_solar_kit

Dimensiona un sistema solar fotovoltaico para red CFE en México (kWp requeridos, paneles ~550W, inversor on-grid o híbrido 120/240V y baterías LiFePO4 opcionales) y devuelve SKUs reales con precio MXN IVA incluido.

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": {
      "monthly_kwh": "<monthly_kwh>"
    },
    "name": "calculate_solar_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthly_kwhYesConsumo eléctrico mensual promedio del recibo CFE en kWh
system_typeNoArquitectura solar: on_grid (interconectado CFE), hybrid (CFE + batería LiFePO4), off_grid (aislado)on_grid
backup_hoursNoHoras de respaldo deseadas en sistemas híbridos/aislados (opcional)
roof_area_m2NoSuperficie útil aproximada de techo en m2 (opcional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose the key output behavior (returns real SKUs with MXN prices, IVA included) and the sizing assumptions baked in (~550W panels, 120/240V on-grid or hybrid inverter, optional LiFePO4). It does not say whether the call is side-effect free, whether prices are live or cached, or how assumptions affect the result.

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, front-loaded with the action and domain, then the deliverable. The long parenthetical packs a lot of spec detail but stays readable and earns its space by naming the actual equipment assumptions.

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?

There is no output schema, so the description must describe the return, and it does: SKUs with prices in MXN including VAT. Combined with a fully documented 4-parameter schema, the only real gap is that it never states what sizing figure (kWp) the caller gets back or how the price quote is scoped.

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%, so all four parameters (monthly_kwh, system_type, backup_hours, roof_area_m2) are already fully documented with ranges and enums. The description only loosely echoes them via the parenthetical about inverter types and optional batteries, adding little beyond the schema.

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?

Uses a specific verb (dimensiona/size) on a specific resource (sistema solar fotovoltaico para red CFE en México) and even states the deliverable (SKUs reales con precio MXN IVA incluido). This is unmistakably different from the sibling recommend_cctv_kit or search_products, though it never names an alternative to sharpen the contrast.

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 stated scope (CFE grid-tied sizing in Mexico) but there is no explicit when-to-use statement, no prerequisite such as 'requires the customer's monthly kWh from a CFE bill', and no when-not guidance. An agent can infer the context but must reason about it rather than being told.

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