Skip to main content
Glama

getecoback-climate-weather

altgeraete_annahme_und_weiterverwendung_beleg

Read-only

Altgeräteannahme und ausdrücklich dokumentierten weiteren Verbleib getrennt festhalten — Avoid inferring reuse or recycling from a handover receipt alone.

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": {
      "altuebergabe_bestaetigt": "<altuebergabe_bestaetigt>",
      "weiterer_beleg": "<weiterer_beleg>",
      "geraetebezug_eindeutig": "<geraetebezug_eindeutig>"
    },
    "name": "altgeraete_annahme_und_weiterverwendung_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
weiterer_belegYesSpäterer belegter Status für dasselbe Altgerät.
geraetebezug_eindeutigYesWeiterer Beleg und Übergabe gehören eindeutig zum gleichen Vorgang?
altuebergabe_bestaetigtYesTatsächliche Annahme des bezeichneten Altgeräts bestätigt?

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 safety and scope are covered. The description adds the substantive semantic constraint that acceptance and further disposition must be captured separately and that reuse must not be assumed from a receipt, which is genuine behavioral context; the wording 'festhalten' is faintly write-sounding but the '…_beleg' naming supports the read-only annotation, so no contradiction is flagged.

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 pairs the purpose with the key caution, with no filler. It is efficient, though the mixed German/English phrasing and the dash construction make it slightly harder to parse than a clean two-sentence split would be.

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 three required parameters, a closed enum and no output schema, the definition covers what to record but says nothing about what the tool returns or how a partial/inconsistent record (e.g. geraetebezug_eindeutig=false) is handled. That is an acceptable gap but not a complete picture for a documentation-verification tool.

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% and the enum values (wiederverwendung_tatsaechlich, vorbereitung_zur_wiederverwendung, verwertung_tatsaechlich, nur_annahme, offen) are fully documented in the schema. The description does not add meaning to any of the three parameters beyond framing why the separate record matters, so the baseline of 3 applies.

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 verb (festhalten/dokumentieren) and a concrete resource pair: Altgeräteannahme plus the explicitly documented further Verbleib. It also implicitly distinguishes itself from a plain handover receipt, though it never names a sibling tool such as altgeraete_abholvorgang_tatsaechliche_uebergabe, so an agent must infer the boundary from context.

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 clause 'Avoid inferring reuse or recycling from a handover receipt alone' signals the situation this tool is for, but only indirectly — there is no explicit 'use this when …' / 'do not use when …' statement and no named alternative to route to. The guidance is implied rather than operational.

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