Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_nutzungsprotokolle_ueberschneidung

Read-only

Zwei nachweislich lückenlos gezählte Einsatzzeiträume mit genau einer bekannten Überlappung zusammenführen — Sum confirmed lifetime-use subsets without counting overlap twice.

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": {
      "gleiches_exemplar_und_einheit": "<gleiches_exemplar_und_einheit>",
      "gruppe_a": "<gruppe_a>",
      "gruppe_b": "<gruppe_b>",
      "doppelte": "<doppelte>",
      "davor_offen": "<davor_offen>"
    },
    "name": "gebrauchtgeraet_nutzungsprotokolle_ueberschneidung"
  }
}

Input Schema

NameRequiredDescriptionDefault
doppelteYesDavon individuell nachvollziehbar in beiden Listen auftauchende gleiche Einsätze.
gruppe_aYesBestätigte einzelne Einsätze der ersten Liste.
gruppe_bYesBestätigte einzelne Einsätze der zweiten Liste.
davor_offenYesIst die Gerätegeschichte vor beiden Listen unvollständig?
gleiches_exemplar_und_einheitYesBeziehen sich beide Protokolle auf dasselbe Exemplar und dieselbe Definition eines Einsatzes?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish a read-only, closed-world calculation. The description adds the arithmetic rule (sum minus the single overlap) but does not explain how the required booleans davor_offen or gleiches_exemplar_und_einheit modify the result, nor what the return value looks like. With annotations covering safety, a 3 is appropriate.

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 core German sentence is front-loaded and efficient; the English sentence is a near-exact translation and therefore somewhat redundant. Still short and readable.

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 five-parameter calculation with full schema coverage and safety annotations, the description covers the operation and its 'complete counts' premise. It leaves unclear how the boolean preconditions affect validity or output, and with no output schema that is a meaningful 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 coverage is 100% and every parameter has a description, so the schema carries parameter meaning. The description reinforces the 'known overlap' condition but adds no syntax or edge-case semantics beyond that, making the baseline 3 appropriate.

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 precise operation: combining two fully counted usage periods with exactly one known overlap and summing without double-counting. It does not name any sibling to distinguish from, so it falls short of 5.

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

Usage Guidelines4/5

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

Specifies the preconditions for use – two demonstrably complete counts and exactly one known overlap – which tells the agent when the tool applies. It offers no explicit exclusions or alternative sibling tools, keeping it at 4.

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