Skip to main content
Glama

getecoback-raumklima

werkstatt_geteilte_hilfsmittel_eindeutiger_bedarf

Read-only

Zwei ungefährliche Werkstattaufgaben mit überschneidendem Bedarf an derselben Sorte zugelassener Hilfsmittel planen — Allocate reusable workshop aids without double-counting already reserved units.

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": {
      "brauchbare_hilfsmittel": "<brauchbare_hilfsmittel>",
      "a_bestaetigt_benoetigt": "<a_bestaetigt_benoetigt>",
      "b_bestaetigt_benoetigt": "<b_bestaetigt_benoetigt>",
      "fuer_a_und_b_anderweitig_gesperrt": "<fuer_a_und_b_anderweitig_gesperrt>"
    },
    "name": "werkstatt_geteilte_hilfsmittel_eindeutiger_bedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_bestaetigt_benoetigtYesFest zugesagte Zahl für Aufgabe A.
b_bestaetigt_benoetigtYesZahl für die gleichzeitig geplante Aufgabe B.
brauchbare_hilfsmittelYesGleichzeitig nutzbare und für beide Aufgaben geeignete Hilfsmittel.
fuer_a_und_b_anderweitig_gesperrtYesDavon separat belegte Hilfsmittel, die für keine der beiden Aufgaben frei sind.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 only hints that reserved units are netted out; it never says whether the call returns a feasible allocation, a maximum count, or a pass/fail verdict — and with no output schema this is the one place that information had to live. It also does not say what happens when demand exceeds supply.

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 compact clauses, front-loaded with the scenario before the allocation constraint. No padding. The mixed German/English phrasing is slightly awkward but costs nothing in length.

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 four-required-parameter, read-only computation with no output schema, the definition covers the inputs' interplay but leaves the result shape and the infeasible case entirely unspecified. An agent knows when the tool applies but not what it will receive back or how to interpret a shortfall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the four parameters are already documented in German. The description nonetheless adds the key semantic relationship the schema lists only individually: 'brauchbare_hilfsmittel' is the shared pool, 'fuer_a_und_b_anderweitig_gesperrt' is subtracted, and the two confirmed demands compete for the remainder — the 'without double-counting' clause ties them together. Baseline-plus rather than baseline.

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 concrete operation (plan two workshop tasks with overlapping aid needs and allocate reusable aids) plus a specific constraint (no double-counting of already reserved units). That distinguishes it from the many other 'geteilte' sibling tools by resource and constraint, though the phrasing 'ungefährliche Werkstattaufgaben' is scenario flavor rather than tool capability.

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 by the scenario: call it when two concurrent tasks draw on the same pool of approved aids. There is no explicit when-not guidance, no named alternative, and no statement of prerequisites (e.g. that quantities must be confirmed/committed), so an agent must infer selection from context alone.

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