Skip to main content
Glama

getecoback-climate-weather

heissluft_zwei_mengen_zonenwahl

Read-only

Zwei bekannte Portionsmengen auf asymmetrischen Schubladen verteilen — Compare both assignments using observed recipe-specific batch capacities.

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": {
      "a_portionen": "<a_portionen>",
      "b_portionen": "<b_portionen>",
      "a_zone1": "<a_zone1>",
      "a_zone2": "<a_zone2>",
      "b_zone1": "<b_zone1>",
      "b_zone2": "<b_zone2>",
      "parallel_geprueft": "<parallel_geprueft>"
    },
    "name": "heissluft_zwei_mengen_zonenwahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_zone1YesBeobachtete passende Portionen von A in Zone 1 für eine Runde.
a_zone2YesBeobachtete passende Portionen von A in Zone 2 für eine Runde.
b_zone1YesBeobachtete passende Portionen von B in Zone 1 für eine Runde.
b_zone2YesBeobachtete passende Portionen von B in Zone 2 für eine Runde.
a_portionenYesGewünschte Anzahl Portionen der Aufgabe A.
b_portionenYesGewünschte Anzahl Portionen der Aufgabe B.
parallel_geprueftYesBeide Kombinationen wurden in der konkret geplanten Anordnung auf zulässige Nutzung geprüft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the tool compares both assignments rather than returning a single placement, which is meaningful behavioral context, but it says nothing about what the comparison yields or how feasibility is reported.

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?

Two tight clauses with the purpose front-loaded and no filler. The dash-separated second clause earns its place by explaining the comparison behavior, though the sentence is compact enough that a little more structure would have helped.

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?

For a seven-parameter computation tool with no output schema, the definition leaves the return value unexplained — an agent cannot tell whether the result is a feasibility verdict, a ranked comparison, or per-zone allocation numbers. The input side is fully covered by the schema, but the output side is not.

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%, with every zone and portion parameter documented in the schema, so the baseline is 3. The description adds only the framing that the zone values are observed batch capacities; it contributes no extra syntax, units, or constraint meaning beyond the schema.

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 specific verb and resource — distributing two known portion quantities across asymmetric drawers — and adds that both assignments are compared using observed batch capacities. That is enough for an agent to grasp the operation, though the phrasing is dense and the hot-air context comes only from the tool name, not the description.

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 implied rather than stated: the tool applies when two known portion amounts must be assigned to zones and observed recipe-specific capacities exist. There is no explicit when-not guidance and no sibling is named as an alternative, leaving the agent to infer the selection context.

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