Skip to main content
Glama

getecoback-climate-weather

q350_tr_etikett_oder_schallpfad_datenzeile

Read-only

Leitet von der gesuchten Geräuschgröße zur passenden Stelle der geprüften Q350-TR-Unterlage — Route a noise claim to the appropriate Q350 TR table.

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": {
      "frage": "<frage>",
      "v0126_belegt": "<v0126_belegt>"
    },
    "name": "q350_tr_etikett_oder_schallpfad_datenzeile"
  }
}

Input Schema

NameRequiredDescriptionDefault
frageYesWas soll belegt werden?
v0126_belegtYesDas Angebotsgerät und sein Quellenbezug wurden mit Q350 TR V0126 abgeglichen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. What the description fails to add is the behavior that matters: what happens when v0126_belegt is false (does the tool refuse, fall back, or return a warning?), and what form the routed result takes. For a decision/routing tool with zero output schema, that is a meaningful gap.

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 short sentence, purpose front-loaded before the alternative. The German/English duplication consumes half the text without adding information, but the total length is still minimal and there is no filler.

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?

With two required parameters, no output schema, and a boolean gate that plausibly controls whether the call is valid at all, the definition should explain the return value and the gating behavior. Neither is present, so an agent knows the tool's intent but not what it will receive or how to handle the false case.

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 the 'frage' enum already documents its three destinations with a question and the boolean's meaning. The description adds no gloss on the enum values (what 'bei_druckpunkt' vs 'am_hoerplatz' imply for the outcome) and no explanation of the V0126 prerequisite. Baseline 3 is appropriate where the schema does all the work.

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 gives a concrete verb and resource: it routes a sought noise quantity ('Geräuschgröße') to the matching passage of the tested Q350 TR document. It does not differentiate itself from the many other q350_tr_* siblings, and it leaves ambiguous what the 'Stelle' output actually is (a table row, a label, a citation), which keeps it short of a 5.

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 statement of when to call this versus the sibling routing tools (e.g. q350_tr_250m3_schallweg_druckpunkte_v0126 or q350_tr_aufstellraum_messbereich_quellenabgleich), and no guidance on whether the V0126 comparison must already have happened. The only hint of a precondition is buried in the parameter schema, not the description.

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