Skip to main content
Glama

getecoback-climate-weather

kondensatschlauch_durchgang_kreuzung

Read-only

Auf einer Skizze prüfen, welche gezeichnete Kondensatschlauchroute den benutzten Durchgang kreuzt — Compare two proposed drain-hose paths against a measured passage band.

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": {
      "durchgang_links_cm": "<durchgang_links_cm>",
      "durchgang_rechts_cm": "<durchgang_rechts_cm>",
      "weg_a_min_cm": "<weg_a_min_cm>",
      "weg_a_max_cm": "<weg_a_max_cm>",
      "weg_b_min_cm": "<weg_b_min_cm>",
      "weg_b_max_cm": "<weg_b_max_cm>"
    },
    "name": "kondensatschlauch_durchgang_kreuzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
weg_a_max_cmYesGrößte Querposition der Strecke A.
weg_a_min_cmYesKleinste Querposition der zusammenhängenden Schlauchstrecke A im betroffenen Bereich.
weg_b_max_cmYesGrößte Querposition der Strecke B.
weg_b_min_cmYesKleinste Querposition der zusammenhängenden Strecke B.
durchgang_links_cmYesLinke Kante des genutzten Streifens auf der Querachse.
durchgang_rechts_cmYesRechte Kante desselben Streifens.

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?

The annotations already state readOnlyHint=true and openWorldHint=false, and the comparison wording is consistent with a read-only check. The description adds that two proposed routes are compared against a measured passage band, but it does not explain the return behavior or how crossing is determined beyond that inference.

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 definition is a single, front-loaded sentence that states the comparison task immediately. The German and English versions duplicate the same content, which is slightly redundant, but the overall structure is efficient.

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 six-parameter geometric comparison with no output schema, the description gives the core purpose but does not specify the shape of the result, such as which route is reported as crossing or what numeric detail is returned. Inputs are well covered by the schema, so the remaining gap is mainly around return semantics.

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%, so all six numeric parameters are documented in the schema itself. The description adds useful framing by calling the paths proposed and the passage band measured, but it does not add parameter-specific meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (prüfen/compare) and specific resources: two proposed drain-hose paths versus a measured passage band. It clearly states the intended check is which drawn condensate-hose route crosses the used passage, which an agent can understand without opening the schema.

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 description implies this is for checking a sketch with proposed hose routes against a measured passage, but it gives no explicit when-to-use versus when-not-to-use guidance and does not name or contrast any alternative tool. Usage is therefore inferable but not fully specified.

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