Skip to main content
Glama

getecoback-climate-weather

split_verbindungsleitung_und_abluft_lesen

Read-only

Bestimme, welche Herstellerzeichnung zur Leitung einer mobilen Split- oder Monoblock-Anlage gehört — Identify the right drawing for a mobile AC connection

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": {
      "bauart": "<bauart>",
      "dokument": "<dokument>",
      "modell_auf_zeichnung": "<modell_auf_zeichnung>"
    },
    "name": "split_verbindungsleitung_und_abluft_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
bauartYesBauweise des angebotenen Geräts
dokumentYesLeitung in der Zubehörzeichnung
modell_auf_zeichnungYesDasselbe genaue Modell steht auf Zeichnung und Angebot

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds nothing further: it does not say whether the tool returns a drawing identifier, a match verdict, or a clarification prompt, and it does not explain how 'unklar' inputs are handled.

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, which is good, but it is a German sentence immediately restated in a compressed English translation that drops details such as 'Monoblock'. Roughly half the text is duplication rather than added information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain what a successful call returns, and it does not — an agent cannot tell whether it receives a drawing name, a set of candidates, or a rejection. For a classifier-style tool with a three-value tri-state enum plus a boolean, that gap matters.

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 two of three parameters are enums, so the schema fully carries parameter meaning. The description contributes no additional semantics about how bauart, dokument, and modell_auf_zeichnung are combined or what a 'false' boolean implies for the result, so the baseline of 3 applies.

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 states a specific verb ('Bestimme'/'Identify') and a specific resource ('welche Herstellerzeichnung zur Leitung einer mobilen Split- oder Monoblock-Anlage'), which is enough to tell this is a drawing-matching tool. It under-delivers slightly on the name's second half ('und_abluft'), since exhaust-hose drawings only appear implicitly via the 'abluftschlauch' enum, and it does not distinguish itself from any siblings.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no prerequisites, and no mention of alternatives or when a result should be treated as inconclusive. The reader can only infer usage from the word 'Bestimme' and from the enum values in the schema.

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