Skip to main content
Glama
Sign In
anker-solix-mcp

anker-solix-mcp

by gkoenig
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_smartmeter_status

Retrieve current grid import/export power and additional status fields from a specific Smartmeter device using its serial number.

Instructions

Get current status for one Smartmeter: grid import/export power and any other fields the Anker cloud API reports for this device.

    Args:
        device_sn: The Smartmeter's device serial number (see
            list_smartmeters or list_devices).

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": {
      "device_sn": "<device_sn>"
    },
    "name": "get_smartmeter_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_snYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 full disclosure burden. It honestly states that the tool returns 'grid import/export power and any other fields the Anker cloud API reports,' indicating an open-ended output. However, it does not explicitly state read-only nature or potential side effects, though the verb 'Get' implies no mutation.

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 concise: one sentence for purpose plus a parameter line. It is front-loaded with the main action and contains no fluff. Every part earns its place.

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?

Given the output schema exists, the description need not detail return values. It covers the tool's purpose and parameter sourcing. The mention of 'any other fields' is vague but truthful. No obvious gaps remain for a simple status retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (device_sn) with 0% schema coverage. The description adds value by explaining 'The Smartmeter's device serial number (see list_smartmeters or list_devices).' This cross-reference aids the agent in obtaining the correct parameter, which goes beyond the schema's minimal title.

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's purpose: 'Get current status for one Smartmeter: grid import/export power and any other fields the Anker cloud API reports for this device.' It uses a specific verb (Get) and resource (Smartmeter status), distinguishing it from sibling tools like list_smartmeters or get_solarbank_status.

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?

The description does not explicitly state when to use this tool versus alternatives. It mentions retrieving status for one Smartmeter but lacks comparison to sibling tools like get_site_overview or get_solarbank_status. The parameter hint to see list_smartmeters or list_devices provides indirect context but no clear usage boundaries.

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