Skip to main content
Glama

getecoback-raumklima

roboter_service_dockversuche_zaehlen

Read-only

Dokumentierte Anfahrten und vollständig bestätigte Dockvorgänge für den Service trennen — Summarize docking reliability from observed attempts.

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": {
      "beobachtete_anfahrten": "<beobachtete_anfahrten>",
      "docking_bestaetigt": "<docking_bestaetigt>",
      "endzustand_offen": "<endzustand_offen>",
      "gleiche_station": "<gleiche_station>"
    },
    "name": "roboter_service_dockversuche_zaehlen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiche_stationYesUnveränderte Station, Bodensituation und relevante Einstellungen?
endzustand_offenYesAnfahrten, bei denen der Endzustand nicht beobachtet wurde.
docking_bestaetigtYesVorgänge mit bestätigtem erfolgreichem Andocken.
beobachtete_anfahrtenYesAnfahrten, die tatsächlich beobachtet wurden.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, self-contained computation. The description adds that observed attempts are treated separately from confirmed dockings and that reliability is derived from observations, which is useful context, but it never says what the operation returns or whether unobserved end states are excluded from the denominator.

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 compact sentence with the key framing front-loaded. The bilingual duplication (German clause plus English gloss) is slightly redundant but does not obscure the content.

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 no output schema, the description should describe the shape of the return value, and it does not — an agent cannot tell whether it receives counts, a reliability ratio, or a breakdown. Parameter documentation is fully covered by the schema, so the remaining gap is the result contract.

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 is already documented, and the baseline is 3. The description hints at the relationship between observed attempts, confirmed dockings and open end states, but does not state the actual computation (e.g. confirmed divided by observed) or how 'gleiche_station' gates the result.

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 gloss 'Summarize docking reliability from observed attempts' gives a verb and a resource, but the German half ('Dokumentierte Anfahrten und vollständig bestätigte Dockvorgänge ... trennen') frames the action as separating categories rather than as counting, which conflicts with the name 'zaehlen'. An agent cannot tell from the text alone whether the result is a count, a ratio, or two separate tallies, and nothing distinguishes it from the many other service-counting siblings.

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?

No statement of when to use this versus alternatives, no prerequisites (e.g. that a single unchanged station is required), and no exclusions. The 'für den Service' phrasing only implies a service-diagnostic context.

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