Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_lang_gelagert_lagerzeit_nachweisgrenze

Read-only

Bekannten und unbelegten Teil der Lagerzeit einer gebrauchten Ware getrennt halten — Bound the documented storage coverage before evaluating a used appliance.

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": {
      "belege_geordnet": "<belege_geordnet>",
      "eingelagert_tag": "<eingelagert_tag>",
      "ausgelagert_tag": "<ausgelagert_tag>",
      "beleg_start": "<beleg_start>",
      "beleg_ende": "<beleg_ende>"
    },
    "name": "gebrauchtgeraet_lang_gelagert_lagerzeit_nachweisgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
beleg_endeYesErster Tag nach der belegten Strecke.
beleg_startYesErster Tag einer lückenlos dokumentierten Lagerstrecke innerhalb dieses Zeitraums.
ausgelagert_tagYesErster Tag nach dem behaupteten Lagerzeitraum.
belege_geordnetYesBetreffen die vorhandenen Angaben dasselbe gelagerte Exemplar?
eingelagert_tagYesErster behaupteter Lagertag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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, consistent with a pure arithmetic check, and the description does not contradict them. The description adds the behavioral concept that documented and undocumented portions are kept separate, but says nothing about what value comes back, whether invalid intervals are rejected, or how belege_geordnet=false is handled.

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 front-loaded, but the German and English wordings restate the same content, so half of the text is redundancy rather than additional value. No structural cues (steps, constraints) are provided.

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?

Five required numeric/boolean parameters are fully described in the schema, which covers inputs adequately. However, with no output schema, the description should have explained what result is produced (a bounded interval, a residual uncovered span, a verdict), and that is absent, leaving the agent unsure what to expect.

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 parameter (beleg_start, beleg_ende, eingelagert_tag, ausgelagert_tag, belege_geordnet) is already documented in the schema. The description adds conceptual framing but no additional parameter-level meaning such as ordering rules or how start/end boundaries are interpreted, so the baseline 3 holds.

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 description names an abstract operation ("Bound the documented storage coverage") on an abstract resource (documented vs. undocumented storage time of a used appliance), so the gist is graspable but no concrete output or computation is stated. It gives no differentiation from the very similar sibling gebrauchtgeraet_laufzeiten_verschiedene_zeitgrenzen or the other Lagerzeit-adjacent tools, leaving the agent to infer which one applies.

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?

"before evaluating a used appliance" supplies a workflow ordering hint, implying this is a pre-check step. There is no statement of when NOT to use it, no named alternative, and no prerequisites, so guidance is implied rather than explicit.

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