Skip to main content
Glama

getecoback-raumklima

stromgruppe_restaufgaben_preiskappung_minimalkosten

Read-only

Unteilbare gemessene Aufträge einem begrenzt günstigen Energieblock zuordnen, dessen Restmenge auch ungenutzt bleiben darf — Optimize two all-or-nothing reservations when cheap capacity is scarce.

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": {
      "guenstig_rest_kwh": "<guenstig_rest_kwh>",
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "guenstig_cent": "<guenstig_cent>",
      "spaeter_cent": "<spaeter_cent>",
      "zeitlich_machbar": "<zeitlich_machbar>"
    },
    "name": "stromgruppe_restaufgaben_preiskappung_minimalkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesVollständig dokumentierter Energiebedarf des unteilbaren Auftrags A.
b_kwhYesVollständig dokumentierter Energiebedarf des unteilbaren Auftrags B.
spaeter_centYesBelegter späterer Preis in Cent/kWh.
guenstig_centYesBelegter Preis im günstigen Block in Cent/kWh.
zeitlich_machbarYesSind beide Buchungen einzeln zeitlich machbar und gemeinsam machbar, falls die Menge reicht?
guenstig_rest_kwhYesVerbleibende Energie im bereits freigegebenen günstigen Nutzungsblock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that the cheap remainder may remain unused rather than forcing full utilization, which is real behavioral context. It does not say what the tool returns or how an infeasible/blocked case is reported, which matters since no output schema exists.

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?

It is two compact clauses with the scoping condition front-loaded and no filler. The bilingual restatement adds a small amount of redundancy, but the core statement is tight and readable.

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?

Wait, incomplete; six required parameters plus a constraint flag and no output schema mean the definition should clarify the decision outcome and how zeitlich_machbar affects feasibility. The description covers the problem setup but not the result or edge-case handling, leaving a real gap for a pure computation tool.

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?

Schema description coverage is 100%, so all six parameters are already documented, establishing the baseline of 3. The description adds framing for the all-or-nothing nature of a_kwh/b_kwh and the optional use of guenstig_rest_kwh, but gives no meaning beyond the schema for prices or the zeitlich_machbar flag.

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 names a concrete operation: allocating two indivisible ('unteilbare', all-or-nothing) jobs to a limited cheap energy block whose remainder may stay unused, framed as a minimal-cost optimization. That is specific enough to distinguish it from sibling allocation tools. It does not explicitly name a sibling to contrast with, keeping it below a 5.

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?

Usage is only implied through the scenario clause 'when cheap capacity is scarce' plus the all-or-nothing constraint; there is no explicit when-to-use/when-not statement and no named alternative. The framing does let an agent infer the situation, but routing guidance is left to inference.

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