Skip to main content
Glama

getecoback-raumklima

geraetepaar_wiederverwendung_gemeinsames_medium

Read-only

Ermitteln, wie stark ein belegter zulässiger Rücklauf den frischen Ressourceneinsatz einer Folgeaufgabe verändert — Trace a recovered medium through two device tasks without double-counting procurement.

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": {
      "erste_frisch_einheiten": "<erste_frisch_einheiten>",
      "wieder_nutzbar_einheiten": "<wieder_nutzbar_einheiten>",
      "zweite_bedarf_einheiten": "<zweite_bedarf_einheiten>",
      "uebertrag_verlust_einheiten": "<uebertrag_verlust_einheiten>",
      "medium_geprueft": "<medium_geprueft>"
    },
    "name": "geraetepaar_wiederverwendung_gemeinsames_medium"
  }
}

Input Schema

NameRequiredDescriptionDefault
medium_geprueftYesIst die konkrete Wiederverwendung zulässig und vollständig belegt?
erste_frisch_einheitenYesTatsächlich frisch eingesetzte Menge an der ersten Aufgabe.
zweite_bedarf_einheitenYesGemessener Bedarf der zweiten Aufgabe in derselben Einheit.
wieder_nutzbar_einheitenYesDavon nach dem ersten Gerät nachweislich unverändert nutzbar und zur zweiten Aufgabe zugelassen.
uebertrag_verlust_einheitenYesTatsächlich beim vereinbarten Übergang nicht mehr nutzbare Menge.

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 safe closed-world computation. The description adds real value by warning against double-counting procurement and requiring that reuse be documented/permitted, but says nothing about the shape of the result (a delta? a ratio?) or what happens when medium_geprueft is false.

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?

Purpose is front-loaded in the first clause, and the sentence is dense but free of filler. The bilingual restatement is slightly redundant, but it usefully restates the constraint (no double counting) rather than merely translating, so the waste is limited.

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?

With five required numeric parameters, no output schema, and a read-only computation, the definition should say what the returned value represents; it describes the intent (reduction in fresh input) but never confirms the result is a quantity, a delta, or a pair of totals. The no-double-counting rule and the documentation requirement are covered, so the gap is moderate rather than severe.

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 description coverage is 100%, so all five parameters are already documented in the schema, and the description adds no per-parameter detail beyond that baseline. However, it does supply the framing that ties the parameters together — two tasks, one transfer, one loss, no double counting — which helps the agent read the five numbers as a coherent computation rather than five isolated scalars.

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 German clause names a specific verb ("Ermitteln") and a concrete quantity: how much a documented permissible return reduces fresh resource input in a follow-up task. The English gloss ("Trace a recovered medium through two device tasks without double-counting procurement") reinforces the two-task trace model. It does not differentiate from any named alternative, which keeps it below 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?

Usage is only implied: the preamble "belegter zulässiger Rücklauf" and the word "Folgeaufgabe" suggest it applies when two device tasks share a reusable medium with documented evidence. There is no explicit statement of when to use this versus other computation tools, and no exclusion or prerequisite beyond what the parameter names imply.

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