Skip to main content
Glama

calculate_battery

Read-onlyIdempotent

Batterijscenario met eigen zonnestroom vóór verliezen, vaste tarieven en degradatie. Geen dynamische handel, capaciteitstarief of financiering. Geen dimensioneringsadvies.

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": {
      "cost": "<cost>",
      "charged": "<charged>",
      "efficiency": "<efficiency>",
      "importPrice": "<importPrice>",
      "exportPrice": "<exportPrice>",
      "annualCost": "<annualCost>",
      "degradation": "<degradation>",
      "years": "<years>"
    },
    "name": "calculate_battery"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
yearsYes
chargedYes
annualCostYes
efficiencyYes
degradationYes
exportPriceYes
importPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful model assumptions — own solar power counted before losses, fixed tariffs, degradation included — but says nothing about units, input validation, or what happens for out-of-range values (e.g. negative exportPrice), which matters for an 8-parameter numeric model.

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?

Three short sentences, assumption first and exclusions after — front-loaded with no filler. It is efficient, though the extreme terseness is part of why parameter meaning is missing; a slightly longer definition would have paid for itself.

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?

With 8 undocumented required parameters, no output schema and no units anywhere, the definition is not sufficient for an agent to call this model correctly. The annotations cover safety but cannot compensate for the missing domain semantics of the inputs.

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?

Schema description coverage is 0% for 8 required numeric parameters, so the description carries the full explanatory burden and largely fails. It only loosely hints at efficiency ('verliezen'), importPrice/exportPrice ('vaste tarieven') and degradation, and gives no units (kWh, EUR, percent per year) or meaning for cost, charged, annualCost and years.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the calculation subject (a battery scenario with own solar power, fixed tariffs and degradation) and rules out dynamic trading, capacity tariff, financing and sizing advice, which helps separate it from siblings like calculate_finance. But it never states the calculation's actual output (savings? payback? self-consumption?) and uses no verb, so the agent must guess what is produced.

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 three 'Geen ...' exclusions give clear when-not-to-use signals for dynamic trading, capacity tariff, financing and sizing questions. However, no positive when-to-use condition is stated and no sibling tool is named as the alternative for the excluded cases, leaving the routing half-specified.

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