Skip to main content
Glama

getecoback-climate-weather

kuehlschrank_zwei_sterne_abteil_eingebettet_volumen

Read-only

Klärt, ob ausgewiesene Zwei-Sterne-Liter zusätzlich zum Hauptfach zählen oder schon darin liegen — Reconcile compartment volume without double-counting a two-star subsection

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": {
      "hauptfach_l": "<hauptfach_l>",
      "zwei_sterne_l": "<zwei_sterne_l>",
      "volumenbezug": "<volumenbezug>"
    },
    "name": "kuehlschrank_zwei_sterne_abteil_eingebettet_volumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
hauptfach_lYesDokumentierter Rauminhalt des genannten Hauptfachs.
volumenbezugYesDie Fachübersicht lässt erkennen, wie die beiden angegebenen Volumen zueinander stehen.
zwei_sterne_lYesSeparat genannte Liter des Zwei-Sterne-Bereichs.

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 usefully adds the anti-double-counting intent, which tells the agent the operation is a reconciliation rather than a plain sum. It does not say what the result looks like, though with no output schema that remains an open gap.

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?

The intent is front-loaded in a single compact sentence, with the English clause serving as a clarifying restatement. The bilingual duplication is mildly redundant but not wasteful enough to obscure the point.

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 small three-parameter, non-destructive computation tool with fully described schema, the description is adequate but leaves the return shape undefined, and no output schema exists to compensate. An agent knows what to feed it but not exactly what it will get back.

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% and the enum for volumenbezug is documented in the schema, so the schema carries the parameter burden. The description restates the two volume concepts and the containment relationship but adds no syntax, defaults, or edge-case rules beyond what the schema already provides. Baseline 3 is appropriate.

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 the specific question resolved: whether declared two-star liters are additional to the main compartment or already contained in it. That is a concrete verb-plus-resource purpose an agent can recognize. It does not distinguish itself from the many other Kühlschrank siblings, so it stops short of 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: the tool applies when a two-star subsection volume must be reconciled against a main-compartment volume. There is no explicit when-to-use framing, no exclusion, and no named alternative among the numerous Kühlschrank label/volume siblings.

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