Skip to main content
Glama

getecoback-raumklima

schallmodell_gemeinsam_messen_rechenrest

Read-only

Vergleicht einen bereits gerechneten Summenpegel mit dem tatsächlich gemessenen gemeinsamen Zustand — Compare a calculated total level with a matching combined measurement.

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": {
      "modell_total_db": "<modell_total_db>",
      "gemeinsam_gemessen_db": "<gemeinsam_gemessen_db>",
      "eigene_toleranz_db": "<eigene_toleranz_db>",
      "belege_abgeglichen": "<belege_abgeglichen>"
    },
    "name": "schallmodell_gemeinsam_messen_rechenrest"
  }
}

Input Schema

NameRequiredDescriptionDefault
modell_total_dbYesErwarteter modellierter Gesamt-LAeq in dB.
belege_abgeglichenYesGleiche Bezugsgröße und Gewichtung, Hörerposition, Gerätestellungen und Intervalle?
eigene_toleranz_dbYesSelbst gesetzte Vergleichsbreite in dB.
gemeinsam_gemessen_dbYesGemessener Gesamt-LAeq im gemeinsamen Zustand in dB.

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 confirms the comparison of model versus measurement but does not disclose what is returned, how tolerance affects the result, or any failure behavior.

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 states the comparison directly. The German and English versions duplicate the same content, which is unnecessary, but there is no further padding.

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?

The tool is simple and read-only, and all required inputs are documented by the schema. However, with no output schema, the description should clarify what the comparison produces and how the tolerance and evidence-match flag influence the result; those gaps keep it at adequate rather than complete.

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 German descriptions for all four inputs. The description only loosely maps the modeled and measured levels and adds no new meaning for eigene_toleranz_db or belege_abgeglichen, so the baseline of 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?

States the specific comparison: a precomputed total level versus a measured combined state. The verb and two resources are clear, but the description does not explicitly distinguish this tool from nearby measurement/comparison siblings.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternative sibling is named. An agent can infer it applies when both a modeled total and a combined measurement exist, but that is implicit only.

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