Skip to main content
Glama

getecoback-raumklima

klima_alternativen_gemeinsames_ausschlusskriterium

Read-only

Für zwei Klimageräte-Alternativen prüfen, welche wegen desselben konkret dokumentierten Aufstellungsbedarfs aus der Auswahl fallen — Compare two alternatives against one actual non-negotiable setup requirement.

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": {
      "notwendigkeit": "<notwendigkeit>",
      "option_a": "<option_a>",
      "option_b": "<option_b>"
    },
    "name": "klima_alternativen_gemeinsames_ausschlusskriterium"
  }
}

Input Schema

NameRequiredDescriptionDefault
option_aYesBeleglage für genau dieses Kriterium bei A.
option_bYesBeleglage für genau dieses Kriterium bei B.
notwendigkeitYesEin einziges zwingendes Kriterium am vorgesehenen Platz.

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 establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the key behavioral premise that both alternatives are judged against the SAME requirement ('gemeinsames'), but it says nothing about how 'offen' evidence is treated, whether both or neither option can be excluded, or what the caller receives back.

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?

One sentence, purpose front-loaded, with the bilingual restatement adding only mild redundancy. No filler beyond the duplicated German/English phrasing.

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?

The three enum parameters are fully documented and there is no output schema, so the description needn't explain return values. Still, for a decision-tool the outcome semantics (what a mixed bestätigt/widersprochen pair or an 'offen' case yields) are the main gap an agent would want covered.

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% with all three parameters enumerated and described, so the baseline is 3. The description contributes one useful nuance – that notwendigkeit is a single shared criterion applied to both A and B – but adds no detail on how bestätigt/widersprochen/offen map to an exclusion decision.

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?

Names a specific operation (comparing two climate-unit alternatives) and a specific criterion type (a documented, non-negotiable installation requirement) that excludes one option. It is distinguishable from single-device checks like klima_aussenteil_stellplatz_check, but it never names a sibling to contrast with, so differentiation is inferred rather than stated.

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?

'Konkret dokumentierten' and 'non-negotiable' imply a precondition – the requirement must be actually evidenced and binding – and 'welche ... aus der Auswahl fallen' implies the comparison/elimination context. However, it gives no explicit when-to-use or when-not-to-use guidance against neighboring placement or datasheet tools.

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