Skip to main content
Glama

getecoback-climate-weather

kochplatten_leerplatz_geschirrwechsel_uebersicht

Read-only

Mit zwei passenden vorhandenen Gefäßen prüfen, welches davon eine kalte Zwischenablage belegt und welches die Fläche freihält — Track cold-vessel availability through a staged cleanup.

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": {
      "gefaesse_bereit": "<gefaesse_bereit>",
      "bleibt_auf_ablage": "<bleibt_auf_ablage>",
      "in_pflege_weg": "<in_pflege_weg>",
      "naechster_abschnitt_benoetigt": "<naechster_abschnitt_benoetigt>"
    },
    "name": "kochplatten_leerplatz_geschirrwechsel_uebersicht"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_pflege_wegYesWeitere zur vorgesehenen Pflege entfernte Gefäße.
gefaesse_bereitYesGleichartige geeignete Gefäße am Beginn.
bleibt_auf_ablageYesDavon nach dem vereinbarten Ablauf weiter belegt.
naechster_abschnitt_benoetigtYesGefäße, die als Nächstes an derselben Stelle bereit sein sollen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 the safety profile is covered. Beyond that, the description adds only atmospheric wording ('staged cleanup') and does not explain how the four input counts interact, what is calculated, or what the result represents — the substantive behavior of a pure-computation tool remains undisclosed.

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

Conciseness3/5

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

It is a single short sentence with no padding, which is good, but it is bilingual and built from metaphor rather than a front-loaded statement of the operation. Brevity here comes at the cost of intelligibility.

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?

The tool takes four required numeric inputs, has no output schema, and the description never says what value or comparison is returned. For a closed-world calculation with a non-obvious result shape, this leaves a real gap an agent cannot close from the structured fields alone.

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 each of the four numeric parameters is already documented in the schema. The description's vessel/staging framing loosely maps onto those parameters but adds no syntax, constraints, or counting rules beyond what the schema supplies; baseline 3 applies.

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 gestures at a vessel/capacity accounting task ('Track cold-vessel availability through a staged cleanup') and mentions checking which of two vessels occupies a cold staging slot versus keeps the surface free. However, the verb is metaphorical ('prüfen', 'Track') and the object ('kalte Zwischenablage', 'Gefäße') is domain jargon, so an agent cannot state precisely what computation is performed or what the tool returns.

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 statement of when to use this tool, when not to, or which sibling handles a related case. The phrase 'through a staged cleanup' hints at a scenario but names no precondition or alternative.

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