Skip to main content
Glama

getecoback-climate-weather

pc_chip_und_ansaugluft_abstand_zerlegen

Read-only

Bei zwei gleichartigen PC-Läufen Temperaturänderung am Chip und an seiner Ansaugluft getrennt bilanzieren — Decompose the observed chip change into inlet and chip-to-inlet terms.

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": {
      "a_chip_c": "<a_chip_c>",
      "a_ansaug_c": "<a_ansaug_c>",
      "b_chip_c": "<b_chip_c>",
      "b_ansaug_c": "<b_ansaug_c>",
      "lasten_und_leistung_vergleichbar": "<lasten_und_leistung_vergleichbar>"
    },
    "name": "pc_chip_und_ansaugluft_abstand_zerlegen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_chip_cYesIntegrierter Chipmesswert in Lauf A nach derselben Messdauer.
b_chip_cYesDerselbe Chipmesswert in Lauf B.
a_ansaug_cYesZeitgleicher äußerer Messwert der Ansaugluft in Lauf A.
b_ansaug_cYesZeitgleicher Wert an derselben Ansaugstelle in B.
lasten_und_leistung_vergleichbarYesGleiche Lastart, Messdauer und Leistung ausreichend 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 agent knows this is a pure local computation with no side effects. The description adds that the result is a separated balance ('getrennt bilanzieren'), which hints at a decomposition rather than a single delta. However, with no output schema, the description leaves the shape of the returned terms, their signs, and their units entirely unexplained.

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 with the comparability condition first and the operation second. The bilingual duplication is mild redundancy, but each clause adds orientation for a German-domain tool and nothing is padded.

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?

Five required numeric/boolean inputs, no output schema, and a non-obvious computed result make this a tool where the return values need at least a sentence. The description establishes the inputs and the comparability constraint but not what the decomposition yields, leaving a real gap for an agent deciding whether to call it.

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 coverage is 100% and every parameter carries a German description defining the measurement point, run, and time alignment, so the schema does the heavy lifting. The tool description only gestures at the parameters as 'chip' and 'Ansaugluft' without adding format, pairing, or tolerance rules. Baseline 3 is appropriate.

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 operation (decomposing a measured chip temperature change) and its two input sources (chip and inlet air) across two comparable runs, in both German and English. An agent can tell it apart from the many measurement/protocol siblings because it is an arithmetic decomposition rather than a measurement or logging tool. It stops short of naming a sibling alternative or the output form, which keeps it from a 5.

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 precondition is stated implicitly: 'Bei zwei gleichartigen PC-Läufen' plus the required boolean lasten_und_leistung_vergleichbar make the comparability requirement clear. There is no explicit when-not guidance, no mention of what to do when the runs are not comparable, and no routing to alternative tools. Usage is inferable but not spelled out.

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