Skip to main content
Glama

getecoback-raumklima

geraetegruppe_aufgabenpaket_vollstaendigkeit

Read-only

Zwei Darstellungen gemeinsamer Leistung unterscheiden: fertige Aufgabenpakete und nicht nutzbare Überkapazität eines Einzelschritts — Infer full paired service from output counts only when pairing is verified.

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": {
      "a_fertig": "<a_fertig>",
      "b_fertig": "<b_fertig>",
      "tatsaechlich_gepaart": "<tatsaechlich_gepaart>",
      "gesamt_wh": "<gesamt_wh>"
    },
    "name": "geraetegruppe_aufgabenpaket_vollstaendigkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_fertigYesZahl abgeschlossener Einheiten des ersten Schritts.
b_fertigYesZahl abgeschlossener Einheiten des zweiten Schritts.
gesamt_whYesEnergie aller Schritte aus dem gemeinsamen Versuchsfenster.
tatsaechlich_gepaartYesZahl belegter Einheiten, die nachweislich beide Schritte durchlaufen haben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 safe, closed-world computation profile is covered. The description adds the substantive rule that paired service may only be inferred when pairing is verified, which is real behavioral context. It still omits what the result looks like and whether the 'unusable overcapacity' branch yields a flag, a count, or an error.

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?

It is short, but the single sentence packs two dense nominal phrases before reaching the actionable clause, so the guidance is not front-loaded. Nothing is padded, yet the abstraction makes it harder to parse than a plain statement of purpose would be.

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?

There is no output schema, so the description is the only place that could explain what the tool returns, and it does not — an agent cannot tell whether to expect a boolean, a residual quantity, or a completeness verdict. For a four-required-parameter computation with no return documentation anywhere else, this is a material gap.

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%, with all four parameters documented in German, so the schema carries parameter meaning fully. The description adds no per-parameter interpretation (for example, how 'tatsaechlich_gepaart' interacts with 'a_fertig'/'b_fertig'), so the baseline 3 applies.

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 description names a conceptual operation ('Zwei Darstellungen gemeinsamer Leistung unterscheiden') and hints at the distinction between completed packages and unusable single-step overcapacity, but it never states concretely what the tool computes or returns. The name suggests a completeness check, yet the description leaves the actual output ambiguous, so an agent cannot tell exactly what invoking it produces.

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?

The only conditional guidance is 'Infer full paired service from output counts only when pairing is verified', which constrains an inference rather than telling the agent when to choose this tool. No sibling is named as an alternative and no exclusion or prerequisite for invoking it is given.

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