Skip to main content
Glama

getecoback-raumklima

werkstatt_druckfreigabe_geteilter_stellbereich

Read-only

Bei zwei einfachen Druckprojekten die gemeinsam vereinbarte Aufsicht und den unabhängigen Zugang zum Abholpunkt prüfen — Register project collection only when the agreed supervision and access are covered.

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": {
      "a_aufsicht": "<a_aufsicht>",
      "b_aufsicht": "<b_aufsicht>",
      "a_abholung": "<a_abholung>",
      "b_abholung": "<b_abholung>",
      "abholungen_zur_gleichen_zeit_moeglich": "<abholungen_zur_gleichen_zeit_moeglich>"
    },
    "name": "werkstatt_druckfreigabe_geteilter_stellbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_abholungYesZugang zur fertigen Probe von A nach vorgesehenen Wartezeiten ist bestätigt.
a_aufsichtYesAufsicht für das erste geplante Projekt ist gemäß Anleitung und Absprache geklärt.
b_abholungYesZugang zur fertigen Probe von B nach vorgesehenen Wartezeiten ist bestätigt.
b_aufsichtYesAufsicht für das zweite geplante Projekt ist nach denselben Regeln geklärt.
abholungen_zur_gleichen_zeit_moeglichYesZwei zeitgleiche Abholungen am selben Ort sind ausdrücklich abgestimmt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, but the description's English sentence uses "Register," a verb that normally implies creating a record — a mixed signal the agent has to resolve on its own. The only genuine behavioral content is the gating condition on supervision/access; nothing is said about what a false boolean produces, whether a partial pass is accepted, or what the caller gets back.

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 short, but it spends its length on a German sentence immediately restated in English, so half the text is redundant. The precondition — arguably the most important information — is buried in the trailing clause rather than front-loaded.

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 five-boolean, fully described, read-only check tool with no output schema, the description covers the subject matter adequately. It is nonetheless incomplete on the decision logic: it never says whether all five booleans must hold, what the result signifies, or how the two projects relate, which is the whole point of a gated check.

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 of the five booleans individually documented (a_aufsicht, b_aufsicht, a_abholung, b_abholung, abholungen_zur_gleichen_zeit_moeglich), so the baseline applies. The description adds no meaning beyond what those field descriptions already state and never maps its "agreed supervision and access" phrasing onto the A/B parameter structure.

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 German clause names a verb ("prüfen") and the resources under review (gemeinsam vereinbarte Aufsicht, unabhängiger Zugang zum Abholpunkt) for two print projects, so the domain is identifiable. However, the English follow-up switches to "Register project collection," which reads like a different operation (record-keeping vs. verification), leaving the actual action ambiguous. Nothing distinguishes it from the many similarly named workshop siblings.

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?

"Register project collection only when the agreed supervision and access are covered" implies a gating precondition for use, which is useful. It does not name any alternative tool or state when NOT to call it, so the agent must infer that from the precondition 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