Skip to main content
Glama
Sign In
Victron VRM MCP Server

Victron VRM MCP Server

by gimi-q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vrm_get_solar_charger_relay_state

Retrieve the relay state and MPPT switching status of solar chargers for a specific installation site.

Instructions

Get solar charger relay state and MPPT switching status.

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": {
      "siteId": "<siteId>"
    },
    "name": "vrm_get_solar_charger_relay_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesInstallation/site ID
instanceNoDevice instance ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as authentication requirements, error handling, or side effects. For a read-only operation, basic transparency is missing.

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?

The description is a single sentence that efficiently conveys the tool's purpose. It is front-loaded and concise, though it could include more detail without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description should provide more context about return values, potential errors, or prerequisite conditions. It is insufficient for a fully informed decision.

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?

The input schema covers both parameters with descriptions (siteId and instance), achieving 100% coverage. The description adds no additional meaning beyond the schema, meeting the baseline but not exceeding it.

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?

The description clearly states 'Get solar charger relay state and MPPT switching status,' specifying the verb and resource. It distinguishes from sibling tools like vrm_get_charger_relay_state by focusing on solar charger relay state, but could elaborate on MPPT switching status.

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 guidance on when to use this tool versus alternatives such as vrm_get_charger_relay_state or vrm_get_gateway_relay_state. The description provides no context for selection.

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