Skip to main content
Glama

getecoback-raumklima

hoerplatz_messhoehen_eigenziel_beide_positionen

Read-only

Prüft einen eigenen Vergleichswert getrennt für Sitz- und Stehhöhe am selben Ort — Test a chosen comparison level at seated and standing ear heights.

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": {
      "sitz_db": "<sitz_db>",
      "stand_db": "<stand_db>",
      "ziel_db": "<ziel_db>",
      "messungen_passend": "<messungen_passend>"
    },
    "name": "hoerplatz_messhoehen_eigenziel_beide_positionen"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitz_dbYesLAeq in selbst gewählter Sitzhöhe in dB.
ziel_dbYesSelbst gewählter Vergleichswert in dB.
stand_dbYesLAeq in selbst gewählter Stehhöhe in dB.
messungen_passendYesGleiche Geräteeinstellung, Messachse, Messdauer und ähnlicher Hintergrund?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's "Prüft" is consistent with a pure evaluation. It adds the constraint that both heights are assessed at the same location, which is useful behavioral context. It does not, however, say what the check produces or what happens when messungen_passend is false.

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?

A single front-loaded sentence covering purpose and scope, with no filler. The bilingual duplication of the same content is mildly redundant but keeps the definition short overall.

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?

No output schema exists, and the description does not indicate what the comparison yields (a difference, a pass/fail, a per-height assessment), which is the main gap for an evaluation tool. The input side is well covered by the schema, so what remains missing is only the result framing.

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%, with each of the four parameters (sitz_db, stand_db, ziel_db, messungen_passend) fully documented, including ranges. The description only restates the seated/standing-in-one-place framing already captured by the schema, adding no extra semantics. Baseline 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?

"Prüft einen eigenen Vergleichswert getrennt für Sitz- und Stehhöhe am selben Ort" names a specific verb (prüfen/test) and a precise scope: a user-supplied comparison level evaluated separately for seated and standing ear heights at one location. The bilingual restatement reinforces rather than blurs this. It does not differentiate itself from any sibling tool, which keeps it out of 5 territory.

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?

Usage is only implied — one would use this when a chosen target value must be checked against both measurement heights. There is no explicit when-to-use, no exclusion, and no named alternative among the many measurement/comparison siblings, so the agent must infer the routing decision.

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