Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_seit_wartung_tatsaechliche_einsaetze

Read-only

Nach einer behaupteten Wartung getrennt ausweisen, welche beobachteten Einsätze davor oder danach lagen — Establish which actual-use records follow maintenance.

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": {
      "wartung_art_und_bezug": "<wartung_art_und_bezug>",
      "davor": "<davor>",
      "tag_gleich": "<tag_gleich>",
      "danach": "<danach>",
      "tage_unerfasst": "<tage_unerfasst>"
    },
    "name": "gebrauchtgeraet_seit_wartung_tatsaechliche_einsaetze"
  }
}

Input Schema

NameRequiredDescriptionDefault
davorYesProtokollierte Einsätze vor diesem Tag.
danachYesEindeutig später protokollierte Einsätze.
tag_gleichYesProtokollierte Einsätze am selben Tag ohne belegte Uhrzeitfolge.
tage_unerfasstYesZusätzliche Tage ohne Nutzungsnachweis nach der Wartung.
wartung_art_und_bezugYesSind die Arbeit, ihr Tag und das konkrete betroffene Bauteil belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read operation, so the description does not need to repeat that. It adds the domain behavior of separating observed uses into before/after maintenance, but it does not explain what is returned or how the counts relate to the separation.

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-loads the maintenance context, but the bilingual duplication is not perfectly aligned: the German says records before or after maintenance, while the English says records that follow maintenance. That inconsistency costs clarity even though the text is brief.

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

Completeness2/5

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

For a read-only analysis tool with five required parameters and no output schema, the description does almost nothing to explain the result or how the five counts are used. It states the general purpose but leaves the agent without enough context to understand the output or the role of parameters like 'tage_unerfasst' and 'wartung_art_und_bezug'.

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 all five parameters are already documented in the input schema. The description clarifies that 'davor' and 'danach' are relative to a claimed maintenance point, but it adds no further meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 uses a specific verb phrase ('getrennt ausweisen' / 'Establish') and names the resource ('beobachteten Einsätze' / 'actual-use records') relative to a claimed maintenance event. It does not differentiate itself from any sibling tool, and the English gloss narrows the scope to records that 'follow' maintenance rather than the original before-or-after framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by 'Nach einer behaupteten Wartung'; there is no explicit when-to-use guidance, no prerequisites, and no pointer to alternatives among the many sibling tools. An agent cannot tell from the description when this tool should be chosen over other maintenance or usage-record tools.

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