Skip to main content
Glama

getecoback-raumklima

q350_tr_waermebereitstellung_pruefregime_lesen

Read-only

Liest die Wärmebereitstellung passend zum Prüfregime und zur dokumentierten Q350-TR-Ausführung — Read the recovered-heat figure under the specific published test regime and variant.

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": {
      "art": "<art>",
      "methode": "<methode>",
      "gleiche_ausgabe": "<gleiche_ausgabe>"
    },
    "name": "q350_tr_waermebereitstellung_pruefregime_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
artYesExakt zugeordnete Ausführung.
methodeYesGesuchte Auswertung aus V0126 S. 3.
gleiche_ausgabeYesDer geprüfte deutsche Quellenstand V0126 ist für diese Angabe belegt.

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 that the read is tied to a documented/published source state, which explains the source-bound nature of the answer. It still does not say what is returned (a numeric figure, a citation, or an error when the "unklar" variant is passed) or what happens when gleiche_ausgabe 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 short, front-loaded definition with the resource and its two scoping dimensions stated first. The German/English duplication is defensible as disambiguation of opaque domain terms, though the English clause largely restates the German one.

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 three-required-parameter, read-only lookup with no output schema, the definition establishes the input contract but leaves the return value underspecified—the agent cannot tell whether it receives a number, a quoted passage, or a document reference. Adequate to call, incomplete for interpreting the result.

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 both enum parameters are documented, so the baseline is 3. The description does modestly useful bridging by linking "Prüfregime" to methode and "Ausführung" to art, but it adds no format, unit, or fallback semantics beyond the schema.

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 specific verb ("Liest") and resource ("Wärmebereitstellung" / "recovered-heat figure") and scopes it to the test regime and Q350-TR variant, so the agent knows this is a targeted lookup rather than a search. It does not differentiate itself from near siblings such as the enthalpy/feuchterückgewinnung tool, and the domain jargon keeps it from being immediately unambiguous.

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?

"passend zum Prüfregime und zur dokumentierten Q350-TR-Ausführung" implies the caller must already know the regime and variant before calling, which is useful implied context. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative when the regime or variant is undetermined.

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