Skip to main content
Glama

getecoback-raumklima

ersatzteil_druck_eignung

Read-only

Bei fehlendem Teil zwischen Modellabgleich, einfachem 3D-Druck und Herstellerhilfe entscheiden — Triage a small missing part or organizer for 3D printing.

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": {
      "use": "<use>",
      "measure": "<measure>",
      "printer": "<printer>"
    },
    "name": "ersatzteil_druck_eignung"
  }
}

Input Schema

NameRequiredDescriptionDefault
useYesEinfacher Organizer, loses Ersatzteil, sicherheitskritische Funktion oder unbekannt.
measureYesVorlage und Aufnahme vollständig vermessen?
printerYesGeeigneter Drucker für einen einfachen Prototyp verfügbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 agent knows this is a closed-domain advisory call with no side effects. The description adds that the outcome is a triage decision, but it never states what that decision looks like or what criteria drive it beyond the three inputs.

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?

A single front-loaded sentence that names the decision and the three candidate paths, with no filler. The mixed German/English phrasing is slightly awkward but does not add length or bury the point.

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 three-enum-parameter advisory tool with no output schema, the description covers the situation, the decision space, and the axes well enough to call it correctly. The one real gap is not describing the shape of the recommendation returned, which matters somewhat for a decision tool but is a minor omission.

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% and every parameter has documented enums, so the schema carries the semantics. The description loosely maps to the three axes (model matching ↔ measuring, 3D printing ↔ printer availability, manufacturer help ↔ critical use) but adds no format or interpretation detail 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 names a concrete decision task (triage a small missing part or organizer toward model matching, simple 3D printing, or manufacturer support), which is more specific than a bare restatement of the name. It does not explicitly distinguish itself from any sibling, but the 'missing part' framing makes the domain clear.

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 trigger context is implied by 'Bei fehlendem Teil' (when a part is missing), which tells the agent the situation to use it in. There is no explicit when-not guidance, no prerequisites, and no named alternative tool, so guidance stays at the implied level.

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