Sunwise Solar

Precio de referencia por kWp y región

precio_por_region

Precio de referencia de instalación solar en Chile por kWp y región, sin IVA y con instalación incluida. Usa esta herramienta para preguntas como '¿cuánto cuesta el kWp en Maule?'. Devuelve el precio por kWp, el total del sistema y la tabla comparativa de las 8 regiones. El campo camino es 'referencia': es el promedio de mercado, no la cotización de una casa concreta (esa la da simular_casa).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "precio_por_region"
  }
}

Input Schema

Name	Required	Description	Default
`kwp`	No	Tamaño del sistema en kWp. Default 4.
`region`	No	Slug o nombre de la región. Default 'rm'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that prices are ex-IVA, include installation, and are market averages rather than per-house quotes, and it names the three things returned (price per kWp, system total, 8-region comparison table). It never explicitly states the tool is read-only, which is the main residual gap for a no-annotation tool.

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?

Four short sentences, front-loaded with the definition before the usage example and the sibling disambiguation. Nothing is padding, though the closing `camino` sentence references an output field that is not formally declared anywhere, which slightly muddies an otherwise tight structure.

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 two-optional-parameter read tool with no output schema and no annotations, the description is nearly sufficient: it covers scope, VAT treatment, and the shape of the response. The only soft spot is the `camino` field, which is discussed without any schema to anchor it.

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 both parameters (kwp, region) and their defaults are already documented in the schema; the description adds no syntax or format detail beyond that. Baseline 3 applies when the schema does the heavy lifting. The `camino` mention refers to a returned field, not an input parameter, so it does not add parameter meaning.

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?

States a specific resource and scope: reference solar installation price in Chile per kWp and region, ex-VAT, installation included. It also distinguishes itself from the sibling `simular_casa`, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete example question it is meant to answer ('¿cuánto cuesta el kWp en Maule?') and explicitly names the alternative (`simular_casa`) for the case it does not cover — a quote for a specific house. When-to-use and when-not-to-use are both present.

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

All Sunwise Solar tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?