Skip to main content
Glama

getecoback-raumklima

geraet_service_ergebnis_gegen_auftrag

Read-only

Nach dem Service vereinbarte, bestätigte und erprobte Funktionen getrennt festhalten — Reconcile the requested repair scope with reported work and checked household functions.

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": {
      "vereinbart": "<vereinbart>",
      "als_erledigt_bestaetigt": "<als_erledigt_bestaetigt>",
      "bestaetigt_und_erprobt": "<bestaetigt_und_erprobt>",
      "aufgabe_gleich": "<aufgabe_gleich>"
    },
    "name": "geraet_service_ergebnis_gegen_auftrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
vereinbartYesEinzeln benannte Aufgaben im Auftrag.
aufgabe_gleichYesEigene Prüfung mit der ursprünglich vereinbarten Aufgabe vergleichbar?
bestaetigt_und_erprobtYesDavon zusätzlich in bereits beobachteter eigener Nutzung erprobt.
als_erledigt_bestaetigtYesDavon laut Rückmeldung abgeschlossen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description is consistent with a read-only reconciliation. It adds the domain behavior of comparing agreed, reported-completed, and tested counts, but does not explain the result shape or what happens when counts are inconsistent, so it adds only moderate context.

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 one sentence and front-loads the post-service reconciliation idea. However, the German and English halves largely duplicate each other, and 'getrennt festhalten' is not clarified, so the sentence is not maximally efficient.

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?

For a four-required-parameter computation with no output schema, the description explains the comparison inputs but not the returned result or how an agent should interpret a mismatch. It is sufficient to attempt a call but leaves important behavioral context unspecified.

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%, so all four parameters are already documented in the schema. The description maps the three numeric fields to agreed/confirmed/tested functions and the boolean to comparability, but adds no units, constraints, or validation rules beyond that conceptual mapping.

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 supplies a specific verb ('Reconcile') and names the quantities being compared: requested repair scope, reported work, and checked household functions. The operation is identifiable, but it does not distinguish this tool from the many sibling service tools, and 'getrennt festhalten' adds slight ambiguity about whether anything is stored.

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?

It gives only the temporal context 'Nach dem Service' and no explicit when-to-use/when-not-to-use rule or named alternative. An agent must infer that this is for post-service reconciliation rather than scheduling, parts tracking, or other sibling service workflows.

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