Skip to main content
Glama

getecoback-climate-weather

schallangabe_split_bauteil_zuordnung

Read-only

Ordnet veröffentlichte Geräuschangaben eindeutig dem Innen- oder Außenteil zu — Assign published split-unit noise figures to the documented component.

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": {
      "zielteil": "<zielteil>",
      "berichtsteil": "<berichtsteil>",
      "genaue_geraetevariante": "<genaue_geraetevariante>"
    },
    "name": "schallangabe_split_bauteil_zuordnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielteilYesBauteil, dessen Angabe gesucht wird.
berichtsteilYesIm Ausschnitt ausdrücklich bezeichnetes Teil.
genaue_geraetevarianteYesStimmen Baureihe, exaktes Modell und Liefermarktausführung überein?

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?

The annotations already establish that this is a read-only, closed-world operation. The description adds that the assignment is 'eindeutig' (unambiguous) and concerns published figures, but it does not explain how ambiguity is handled, what happens when the report explicitly marks a part as 'unklar,' or what the result looks like.

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 description is a single sentence with the core purpose front-loaded, and it avoids unnecessary detail. The bilingual German/English phrasing is slightly redundant but appropriate for a bilingual tool context.

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 simple three-parameter classification tool, the description covers the intent adequately. It does not describe the return value or how edge cases such as 'unklar' are resolved, and there is no output schema to compensate for that omission.

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 three parameters and their enums are already well documented in the input schema. The description adds only high-level context about indoor/outdoor components and does not elaborate on parameter meanings 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 states a specific verb, 'assigns,' and a specific resource, 'published split-unit noise figures,' with the target being the documented indoor or outdoor component. This is clear enough for an agent to understand the tool's function, though it does not explicitly differentiate itself from sibling tools.

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 use case is implied by the description: assign published noise figures to the correct component. However, there is no explicit when-to-use, when-not-to-use, prerequisite, or named alternative among the siblings.

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