Skip to main content
Glama

getecoback-raumklima

mobilgeraet_schallplatz_sichtlinie_messbeleg

Read-only

Trennt zwei tatsächlich gemessene Hörplätze nach vorhandener direkter Sichtlinie zur Quelle — Compare two existing acoustic positions classified by observed line of sight.

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": {
      "sichtplatz_db": "<sichtplatz_db>",
      "verdeckter_platz_db": "<verdeckter_platz_db>",
      "normale_aufstellung": "<normale_aufstellung>",
      "hintergrund_aehnlich": "<hintergrund_aehnlich>"
    },
    "name": "mobilgeraet_schallplatz_sichtlinie_messbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
sichtplatz_dbYesLAeq am beobachteten Platz mit direkter Sichtlinie in dB.
normale_aufstellungYesVorhandene nicht umgestellte Hindernisse, gleicher Modus und vergleichbarer Abstand?
verdeckter_platz_dbYesLAeq am natürlich verdeckten Platz in dB.
hintergrund_aehnlichYesHintergrund beider Messfenster vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 contributes the meaningful extra that this operates on already-measured values rather than predicting propagation, but it says nothing about how mismatched or invalid inputs (e.g. hintergrund_aehnlich=false) are handled, nor 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?

Two short clauses with the operation front-loaded and no filler. The German/English duplication is slightly redundant but serves readability given the cryptic tool name, so it mostly earns its place.

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 four-required-parameter comparison tool with no output schema, the definition omits the one thing an agent most needs: what comes back and in what form. Safety and input semantics are adequately covered by annotations and schema, so the gap is contained but real.

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 (both LAeq values, the setup flag, the background-similarity flag) are already documented in the schema. The description only restates the line-of-sight split that the schema fields already encode, adding no format, unit, or tolerance detail beyond it; 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?

The description names a concrete operation (comparing/separating two measured listening positions) and the discriminating criterion (observed direct line of sight to the source), and the English gloss makes the opaque German tool name interpretable. It falls short of 5 because it never says what the comparison produces (a delta, a classification, a verdict) and does not distinguish itself from lookalike siblings such as infrarot_sichtlinie_arbeitsplatz.

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, when-not-to-use, or named alternative anywhere in the definition. The phrase 'tatsächlich gemessene' hints that only real measurement pairs qualify, but that is an input precondition, not routing guidance, and the agent is left to infer the scenario on its own.

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