Skip to main content
Glama

energy_add_battery_source

Add a battery source to the Energy Dashboard by providing the charge and discharge statistics.

Instructions

Add a battery source to the Energy Dashboard (both charge stat_energy_to and discharge stat_energy_from).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stat_energy_fromYes
stat_energy_toYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description only conveys the basic action. It does not disclose side effects (e.g., whether it replaces an existing battery source), required permissions, or the structure of the output, despite an output schema existing.

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, front-loaded sentence with no superfluous information, effectively communicating the tool's purpose and parameter roles.

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

Completeness3/5

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

The description covers the core functionality and parameter semantics but lacks usage guidelines and behavioral transparency. Given the tool's simplicity and presence of an output schema, it is minimally adequate but not comprehensive.

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?

The description adds meaning by associating stat_energy_from with discharge and stat_energy_to with charge, which is not present in the schema (0% coverage). However, it does not specify parameter formats or data types beyond strings.

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 action 'Add a battery source' to the Energy Dashboard and specifies the two parameters for charge and discharge, distinguishing it from other energy source tools like energy_add_solar_source or energy_add_grid_consumption.

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 is provided on when to use this tool versus alternatives (e.g., adding solar or grid), nor any conditions or prerequisites for using it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fistacho/ha-nexus-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server