Skip to main content
Glama

SolarDesk

diagnose_inverter_fault

Look up a solar / ESS / EV inverter or charge-controller fault code and return the normalised meaning, likely causes, checks, parts, safety notes, and source. Cite the source and hard-stop (requires_qualified_installer) on safety-critical faults.

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": {
      "brand": "<brand>",
      "code": "<code>"
    },
    "name": "diagnose_inverter_fault"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code shown on the display or app, e.g. 'Err 17', 'VE.Bus Error 8'
brandYesInverter/charger brand
modelNoOptional model or series
symptomNoOptional free-text symptom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well by disclosing returned categories, source citation, and a safety-critical hard-stop using requires_qualified_installer. It does not explicitly state read-only behavior or how unknown codes are handled, but the critical safety behavior is clear.

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?

The description is two dense sentences with the core action and output fields front-loaded. Every phrase adds useful information, including source citation and the safety hard-stop.

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 definition is complete enough for a fault-code lookup: it explains the inputs implicitly through the schema and enumerates the returned fields since no output schema exists. It could say more about unknown-code behavior, which keeps it from being fully exhaustive.

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 coverage is 100%, so the input schema already describes the brand, code, model, and symptom fields. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 uses a specific verb, "look up," and a precise resource, an inverter or charge-controller fault code, with explicit domain scope covering solar, ESS, and EV equipment. It also states the return contents, making the tool's purpose immediately clear.

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

Usage Guidelines4/5

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

The context clearly indicates the tool is for interpreting a specific fault code and brand. It gives no explicit exclusions or alternative tools, but the usage context is sufficiently clear.

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