Skip to main content
Glama

Household workload balance

get_household_balance
Read-only

Check how the household workload is split and get the top tasks that could be handed from the most-overloaded member to the most-underloaded one. Returns is_balanced, the overloaded member, the suggested target, and ranked candidate tasks (highest-impact first). Read-only — use it to reason before proposing any reassignment.

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_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

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 cover readOnlyHint, destructiveHint, and openWorldHint, so the safety profile is supplied. The description adds genuine value beyond them by disclosing the response contents (is_balanced, overloaded member, suggested target, ranked candidate tasks with highest-impact ordering), though it is silent on how ties or missing workload data are handled.

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?

Two tight sentences with no filler: the analytical purpose and output shape come first, the read-only guidance last. Every clause carries information an agent needs.

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?

With no output schema, the description usefully enumerates the key return fields, which is the main completeness requirement here. The remaining gap is the unexplained limit parameter, which is minor but real for a tool whose output can be truncated.

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

Parameters2/5

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

The single parameter `limit` has zero schema description coverage, and the description never mentions it. An agent cannot tell from either source that limit caps the number of ranked candidate tasks returned (default 5, max 10), so the one parameter is effectively undocumented.

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?

States a specific verb and resource combination: assess household workload split and return handoff candidates from the most-overloaded to most-underloaded member. The scope is precise enough to distinguish it from adjacent analytics siblings like get_household_energy or get_schedule_conflicts, but no sibling is named for contrast.

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

Usage Guidelines4/5

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

"Use it to reason before proposing any reassignment" gives clear when-to-use context and implicitly positions it as a pre-step to a mutation tool such as assign_owner. It does not name that alternative or state when-not to call it, so the routing is implied rather than explicit.

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