Skip to main content
Glama

Household energy levels

get_household_energy
Read-only

Read the household's logged energy for a day (default today): overall level, a short summary, and each tracked member's name + level. Read-only; use to pace plans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_household_energy"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional ISO calendar date, YYYY-MM-DD. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description's 'Read-only' restates it. What the description adds beyond annotations is the return shape (overall level, summary, per-member name and level) and the default-to-today behavior, which is genuinely useful given there is no output schema.

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?

A single compact sentence: the action and default come first, the returned fields next, and the read-only/pacing note last. There is no filler or redundancy.

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 zero-required-parameter read tool with a fully documented schema and covering annotations, the description supplies the missing piece, namely what the response contains. Only the absence of sibling routing guidance keeps it from being fully complete.

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?

There is one optional parameter with 100% schema coverage that already documents the ISO YYYY-MM-DD format and the today default. The description repeats the default rather than adding new meaning, so the baseline of 3 for high-coverage schemas applies.

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 states a specific verb and resource (reads the household's logged energy) and enumerates what comes back: overall level, a short summary, and each tracked member's name and level. It is clearly not a balance, budget, or profile tool, though it never names a sibling to contrast with.

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 trailing clause 'use to pace plans' gives an implied usage context, which is more than nothing. However, there is no explicit statement of when not to use it, nor any pointer to alternatives such as get_household_balance or get_household_context_profile for related household signals.

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