Skip to main content
Glama
Sign In
viaris-mcp

viaris-mcp

by Nolex13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_solar_config

Configure solar charging by enabling or disabling and setting priority.

Instructions

Enables or disables solar charging and sets its priority.

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": {
      "enabled": "<enabled>"
    },
    "name": "set_solar_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
chargerNoCharger name. Unnecessary if only one is configured.
enabledYestrue to enable solar charging.
priorityNoPriority of the solar source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/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 states what the tool does (enable/disable solar charging, set priority) but does not disclose side effects, idempotency, or potential interactions with other settings. This is adequate for a simple setter but lacks depth.

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 a single, concise sentence that covers the core functionality without unnecessary words. It is well-structured and immediately understandable.

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 simple setter, the description and schema are sufficient to understand how to invoke it. There is no output schema, which is acceptable for a mutating action, but the description does not mention return values or error conditions, leaving minor gaps for edge cases.

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?

All three parameters have descriptions in the schema (charger, enabled, priority), and the tool description reinforces their purpose. However, the descriptions are minimal—priority lacks explanation of its numeric range or default behavior, and charger is only vaguely described as a name.

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 enables or disables solar charging and sets its priority, using specific verbs and a clear resource. It is distinguishable from sibling tools like set_charging_allowed and set_home_power_limit.

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

Usage Guidelines2/5

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

No explicit guidance is given on when to use this tool versus alternatives such as set_charging_allowed or set_home_power_limit. The description implies it is for solar-specific settings but does not clarify appropriate contexts or prerequisites.

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

Deploy Server

Other Tools