Skip to main content
Glama

getecoback-climate-weather

heissluft_portionen_nachlaufprobe

Read-only

Beobachtete Portionen beim ersten Servieren und die erst später verfügbaren Portionen getrennt zählen. — Count first-service portions and portions deferred to a later round.

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": {
      "portionen_geplant": "<portionen_geplant>",
      "portionen_erster_termin": "<portionen_erster_termin>",
      "portionen_spaeter": "<portionen_spaeter>",
      "abstand_minuten": "<abstand_minuten>"
    },
    "name": "heissluft_portionen_nachlaufprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
abstand_minutenYesBeobachteter Abstand zwischen erstem und letztem Servieren, bei einem Termin null.
portionen_geplantYesGeplante gleich große Portionen für denselben Anlass.
portionen_spaeterYesWeitere für diesen Anlass tatsächlich später bereitgestellte Portionen.
portionen_erster_terminYesDavon beim ersten Servieren tatsächlich bereitgestellte Portionen.

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?

The read-only and closed-world annotations cover the safety profile, while the description adds the useful rule that initial and deferred portions must remain separate observed counts. It does not explain any calculation, consistency checks, treatment of the time gap, or the returned assessment.

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 description is very short and front-loads the essential distinction between first-service and deferred portions. The English sentence largely duplicates the German one, so it aids bilingual readability but adds no new operational guidance.

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 four flat, fully documented numeric inputs and read-only annotations, the definition is adequate to collect the requested observations. Because there is no output schema, the absence of any statement about what the probe computes or returns, together with the unexplained role of the serving interval, leaves a notable completeness gap.

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 coverage is 100%, so all four required inputs and their constraints are already documented, establishing the baseline score. The description reinforces portionen_erster_termin and portionen_spaeter but adds nothing substantive about portionen_geplant or abstand_minuten 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 gives a concrete action and resource: separately count portions served initially and portions deferred to a later round. That narrows the tool to split-service portion observations, although it neither explains what the "Nachlaufprobe" concludes nor differentiates it from sibling heissluft tools.

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 first-service/later-round wording implies use when portions for one occasion are provided across multiple serving rounds. It gives no explicit when-to-use condition, exclusion, prerequisite, or alternative, and does not itself identify the single-appointment case with a zero interval.

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