Skip to main content
Glama

getecoback-raumklima

daikin_rollenangebot_satz_und_einzelangabe_abgleichen

Read-only

Rechnet bestätigte Satz- und Einzelmengen nur dann zusammen, wenn sie getrennt geliefert werden — Reconcile box and individual quantities only when the offer proves distinct units.

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": {
      "saetze": "<saetze>",
      "einzelne": "<einzelne>",
      "angabe_getrennt": "<angabe_getrennt>",
      "genaues_angebot": "<genaues_angebot>"
    },
    "name": "daikin_rollenangebot_satz_und_einzelangabe_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
saetzeYesAnzahl ausdrücklich bestätigter originaler KKS080B41-Sätze.
einzelneYesZusätzlich genannte bestätigte einzelne Rollen.
angabe_getrenntYesBeziehung der genannten Einzelrollen zu den Sätzen.
genaues_angebotYesSchriftlicher Lieferumfang und die genaue deutsche Teilekennung sind abgeglichen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered; the description adds that this is a conditional aggregation that should not fire on overlapping quantities. It does not say what the tool returns or does when the 'distinct units' condition fails (zero, unchanged, or rejection), which is the key behavioral unknown for a read-only check.

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?

Short and front-loaded with the condition, but it is bilingual duplication where the English half is a near-literal restatement rather than added precision, and 'proves distinct units' introduces ambiguity instead of removing it.

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 four required parameters, no output schema, and an enum discriminating three relationships, the definition covers the main gating logic but omits the outcome of the non-distinct case and any hint at the expected return, leaving a real gap for an agent deciding whether to call it.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description goes slightly beyond by framing the relationship between `saetze` and `einzelne` as conditional on separate delivery, which gives the agent the intent behind `angabe_getrennt`. It still does not clarify the `offen` or `genaues_angebot` semantics beyond the schema.

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 names a specific operation (adding/reconciling confirmed set and individual quantities) and the resource domain (Saetze vs. Einzelrollen), plus a gating condition. It is specific enough to separate it from generic 'abgleichen' siblings, though it never names which sibling to prefer and the phrase 'proves distinct units' is fuzzy.

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 one conditional cue ('nur dann ... wenn sie getrennt geliefert werden'), which tells the agent the reconciliation is only valid when the quantities are supplied separately. However that condition is essentially a restatement of the `angabe_getrennt` enum value, and no when-not case or alternative tool is offered.

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