Skip to main content
Glama

getecoback-raumklima

saugwischer_service_testlauf_abbruchquote

Read-only

Beobachtete vollständige Durchgänge und Abbrüche nach Herstellerpflege für den Service vergleichen — Compare documented completion rates before and after the recorded care step.

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": {
      "laeufe_vorher": "<laeufe_vorher>",
      "abbrueche_vorher": "<abbrueche_vorher>",
      "laeufe_nachher": "<laeufe_nachher>",
      "abbrueche_nachher": "<abbrueche_nachher>",
      "gleiche_aufgabe": "<gleiche_aufgabe>"
    },
    "name": "saugwischer_service_testlauf_abbruchquote"
  }
}

Input Schema

NameRequiredDescriptionDefault
laeufe_vorherYesAnzahl protokollierter Durchgänge vor der Pflege.
laeufe_nachherYesAnzahl protokollierter Durchgänge danach.
gleiche_aufgabeYesBoden, Laufaufgabe, Modus und Definition des Abbruchs vergleichbar?
abbrueche_vorherYesDavon vor dem vorgesehenen Ende abgebrochen.
abbrueche_nachherYesDavon vor dem vorgesehenen Ende abgebrochen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 safety profile is covered and the description only needs to add scope, which it does by anchoring the computation to the recorded care step. However, it never says what the tool returns (rates, deltas, a verdict), nor what happens when gleiche_aufgabe is false — whether it refuses the comparison or merely flags it.

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?

The purpose is front-loaded and there is no filler, but the identical sentence is repeated in German and English, which roughly doubles the length without adding information. A single well-formed sentence would have sufficed.

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

Completeness4/5

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

With five required numeric parameters and no output schema, the definition should still tell the agent what kind of result to expect; it omits the return shape and the role of the comparability flag. That is a real gap, though the fully described input schema covers most of what an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and every parameter carries a German description, so the schema already does the parameter work; the description still adds the before/after-care framing that makes clear what 'vorher' and 'nachher' are measured against. Since the schema is fully self-documenting, this is a case where baseline is met and the description adds the contextual anchor rather than competing with it.

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?

States a specific verb (vergleichen/compare) and a specific resource (vollständige Durchgänge und Abbrüche vor/nach der Herstellerpflege), so an agent can tell this is a pre/post abort-rate comparison rather than a raw measurement. It stops short of naming which sibling to use instead, but the purpose itself is unambiguous.

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: 'für den Service' plus the before/after framing suggests it is for evaluating whether a care step improved completion. There is no explicit when-to-use condition, no exclusion, and no pointer to a sibling for the case where only one period is available.

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