Skip to main content
Glama

getecoback-raumklima

werkstatt_probedruck_nacharbeit_serienentscheid

Read-only

Aus wiederholt beobachteter Nacharbeit entscheiden, ob ein einfacher Trenner schon in kleiner Serie taugt. — Decide whether a small run of drawer dividers fits your measured rework budget.

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": {
      "gepruefte_trenner": "<gepruefte_trenner>",
      "nachbearbeitet": "<nachbearbeitet>",
      "verworfen": "<verworfen>",
      "minuten_nacharbeit": "<minuten_nacharbeit>",
      "maximal_minuten_je_verwendbar": "<maximal_minuten_je_verwendbar>"
    },
    "name": "werkstatt_probedruck_nacharbeit_serienentscheid"
  }
}

Input Schema

NameRequiredDescriptionDefault
verworfenYesAndere nicht verwendbare Probe-Trenner.
nachbearbeitetYesDavon erst nach ungefährlicher Nachbearbeitung verwendbare Trenner.
gepruefte_trennerYesGeprüfte Probe-Trenner derselben Geometrie und Herstellung.
minuten_nacharbeitYesGesamte aktive Nachbearbeitungszeit der akzeptierten Proben.
maximal_minuten_je_verwendbarYesEigene Grenze für aktive Nachbearbeitung je verwendbarem Trenner.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add decision logic. It does add that the verdict is judged against the caller's own rework budget, but it never states how the comparison is made (per-usable-part minutes vs. the supplied limit) or what an inconclusive outcome looks like.

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?

The definition is short and the decision is front-loaded in the first clause. However, the sentence is given twice, once in German and once in a near-verbatim English rendering, so roughly half the text is duplicated rather than earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only computation over five fully documented numeric parameters with no output schema, the description supplies the one thing the schema cannot: that the result is a suitability decision measured against the caller's own tolerance. It stops short of describing result shape or handling of degenerate inputs, but nothing critical to invoking it is missing.

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 every one of the five required parameters is already documented in the schema; baseline is 3. The description adds only the loose framing that the inputs represent repeated observations of the same geometry and a self-set budget, which mildly reinforces the schema wording without adding new semantics.

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 specific act ('entscheiden' / 'Decide whether') applied to a concrete object (a small run of drawer dividers) using a stated input basis (observed rework). An agent can tell this is a go/no-go suitability verdict, not a measurement or a probe-inspection tool. It does not name or contrast any sibling, so it stops short of a 5.

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 phrase 'aus wiederholt beobachteter Nacharbeit' implies a precondition: only call this after rework has been observed more than once. That is implicit usage guidance rather than an explicit when/when-not rule, and no alternative (e.g. the sibling probe or return-check tools) is offered for other situations.

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