Skip to main content
Glama

getecoback-climate-weather

heissluft_mitnutzung_einzelschublade_kompromiss

Read-only

Eine flexible Küchenaufgabe zwischen vorab bestätigten Startmöglichkeiten und einer strikt belegten Schublade vermitteln — Rank a flexible basket use against an immutable reservation.

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": {
      "fest_ab_min": "<fest_ab_min>",
      "fest_bis_min": "<fest_bis_min>",
      "flexibel_ab_min": "<flexibel_ab_min>",
      "betriebsblock_min": "<betriebsblock_min>",
      "zugesagt_bis_min": "<zugesagt_bis_min>"
    },
    "name": "heissluft_mitnutzung_einzelschublade_kompromiss"
  }
}

Input Schema

NameRequiredDescriptionDefault
fest_ab_minYesBeginn der festen Belegung auf der gemeinsamen Minutenachse.
fest_bis_minYesEnde der festen Belegung einschließlich vorgeschriebener Freigabe.
flexibel_ab_minYesFrühester möglicher Start der flexiblen Nutzung.
zugesagt_bis_minYesZeitpunkt, vor dem auch der flexible Einsatz beendet sein muss.
betriebsblock_minYesDeren unteilbare gemessene Belegung bis zur Freigabe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only a conceptual framing ('rank a flexible basket use against an immutable reservation') and does not explain what is computed, whether feasibility or ranking is returned, or any constraints beyond the metaphor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but poorly structured: it is bilingual, mixes metaphors ('Küchenaufgabe', 'basket use', 'drawer'), and front-loads an unclear concept instead of a concrete operation. The duplication in German and English does not earn its place.

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?

For a five-parameter scheduling/ranking tool with no output schema, the description is incomplete: it does not explain what the tool returns or how the fixed/flexible time values are combined. The detailed parameter schema helps, but the overall operation remains opaque.

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 each time parameter documented in German. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies for a fully documented schema.

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 uses a vague metaphor ('Eine flexible Küchenaufgabe ... vermitteln') and an English gloss ('Rank a flexible basket use against an immutable reservation') that hints at a ranking/computation but never states the concrete resource or operation. An agent can infer it involves comparing flexible use against fixed reservations, but not exactly what is returned or how it differs from sibling scheduling tools.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The phrase 'between pre-confirmed start options and a strictly occupied drawer' implies a scheduling context, but it does not tell an agent when this tool is the right choice versus the many sibling oven/airflow tools.

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