Skip to main content
Glama

getecoback-raumklima

balkontuer_terrassenweg_haeufige_konflikte

Read-only

Bei zwei tatsächlich erprobten Terrassenaufbauten ungeplantes Umräumen je Türdurchgang vergleichen — Compare real doorway interruptions across two terrace setups.

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": {
      "durchgaenge_a": "<durchgaenge_a>",
      "durchgaenge_b": "<durchgaenge_b>",
      "umraeumen_a": "<umraeumen_a>",
      "umraeumen_b": "<umraeumen_b>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "balkontuer_terrassenweg_haeufige_konflikte"
  }
}

Input Schema

NameRequiredDescriptionDefault
umraeumen_aYesDurchgänge in A, bei denen Gegenstände tatsächlich neu abgestellt wurden.
umraeumen_bYesEntsprechende Durchgänge in B.
vergleichbarYesGleiche Benutzung, Gegenstände und Beobachtungsregeln vor Ort?
durchgaenge_aYesVollständig beobachtete übliche Türdurchgänge mit Aufbau A.
durchgaenge_bYesVollständig beobachtete übliche Türdurchgänge mit Aufbau B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety profile is covered and the description only needs to add what the annotations cannot. It adds that inputs must come from two actually-tested setups, which is useful, but says nothing about the returned comparison (rate, ratio, difference) or the behaviour when the comparability flag is false - a notable gap for a pure computation tool with no output schema.

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?

The description is short and front-loaded with the comparison target, but it is a single sentence repeated verbatim in German and English, so roughly half the text is a translation of the other half. The German clause is also dense and slightly elliptical, leaving the exact comparison metric implicit.

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 five required numeric/boolean parameters fully documented and read-only annotations present, the definition is close to complete, but the absence of an output schema means the description should have explained what comparison result comes back and how the 'vergleichbar' guard affects it. Those two omissions are the only real shortfalls for a tool of this complexity.

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% and each of the five parameters carries its own German description, so the schema does all the semantic work. The tool description adds no additional parameter meaning beyond echoing the idea of doorway passes and unplanned rearranging, which is the baseline 3 case.

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 verb ('vergleichen' / compare) and a specific resource ('ungeplantes Umräumen je Türdurchgang' across two terrace setups), so the agent knows this is a two-condition comparison of observed doorway-clearance events. It does not need sibling differentiation because no sibling in the supplied list performs a comparison of this kind.

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?

The phrase 'bei zwei tatsächlich erprobten Terrassenaufbauten' implies a precondition (both setups must be genuinely field-observed rather than hypothetical), and the required 'vergleichbar' flag reinforces that comparability must be established. However, there is no explicit statement of when to call this instead of doing something else, and no statement of what happens when 'vergleichbar' is false.

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