Skip to main content
Glama

getecoback-raumklima

geraet_schallrichtung_gleicher_radius_seitenvergleich

Read-only

Vergleicht seitliche Pegel mit der Vorderseite, wenn alle Punkte gleich weit vom Gerät lagen — Compare measured side levels relative to the front at a matching distance.

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": {
      "vorn_db": "<vorn_db>",
      "links_db": "<links_db>",
      "rechts_db": "<rechts_db>",
      "gleiche_geometrie": "<gleiche_geometrie>"
    },
    "name": "geraet_schallrichtung_gleicher_radius_seitenvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorn_dbYesLAeq vor dem Gerät in dB.
links_dbYesLAeq links in dB.
rechts_dbYesLAeq rechts in dB.
gleiche_geometrieYesGleicher Abstand, Höhe, Modus und vergleichbarer Hintergrund an allen Punkten?

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, so the safety profile is covered. The description adds the equal-radius validity condition beyond the annotations, but says nothing about the result of the comparison (e.g., a left/right delta in dB, which side is louder) even though there is no output schema.

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 definition is short and front-loaded, but the German sentence is repeated verbatim in English, so half the text adds no information. A single bilingual statement or a compact one-liner would earn the same place with less waste.

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

Completeness4/5

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

With a simple four-scalar schema and read-only annotations, the description covers what is compared and under what geometric condition, which is largely sufficient. The main remaining gap is that no output schema exists and the description does not say what the comparison returns.

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 four parameters (vorn_db, links_db, rechts_db, gleiche_geometrie) are already documented in the schema. The description restates the shared-distance condition that maps to gleiche_geometrie but adds no new parameter-level meaning such as expected units handling or tolerance.

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 names a concrete operation: comparing measured side levels against the front level under an equal-distance condition. That is specific enough for an agent to know exactly what is computed, though it does not name any sibling tool it should be chosen over (none of the listed siblings appears to do the same acoustic comparison).

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 clause 'wenn alle Punkte gleich weit vom Gerät lagen' implies the validity precondition for using this tool, which is useful context. However, it gives no explicit when-not guidance, no alternative tool for unequal geometry, and no statement about what to do if the condition fails.

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