Skip to main content
Glama

getecoback-raumklima

pc_sensorquellen_cpu_gpu_wechsel_nicht_verketten

Read-only

Nach Wechsel der Monitoring-Ansicht klären, welche alten und neuen Sensorreihen für CPU und GPU getrennt fortgeführt werden können — Preserve independent CPU and GPU log continuity after a telemetry-view change.

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": {
      "cpu_identitaet": "<cpu_identitaet>",
      "gpu_identitaet": "<gpu_identitaet>",
      "temperaturart_gleich": "<temperaturart_gleich>"
    },
    "name": "pc_sensorquellen_cpu_gpu_wechsel_nicht_verketten"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpu_identitaetYesDokumentierter Abgleich der CPU-Sensorquelle in beiden Ansichten.
gpu_identitaetYesDokumentierter Abgleich der GPU-Sensorquelle in beiden Ansichten.
temperaturart_gleichYesSind Format, Maßeinheit und bei allen identischen Quellen zugleich die Ableseart 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 the decision context (separate continuation of CPU vs GPU series after a view change), but says nothing about what the tool returns or how the verdict is used, leaving a gap beyond annotations.

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?

Effectively two clauses: trigger condition front-loaded, then the action and its purpose. No redundant filler, though the German/English duplication is slightly verbose.

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 small read-only determination tool with three fully documented parameters and no output schema, the description covers the scenario and intent adequately. It is thin on what outcome the agent should expect, which is the main missing piece.

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%, with enum values and descriptions for cpu_identitaet/gpu_identitaet and a documented boolean. The description supplies the reasoning frame (old vs new rows, separate continuation) but does not elaborate the 'offen' state or how temperaturart_gleich combines with the identity fields, so it adds only marginal meaning over 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?

States a specific decision task: after a monitoring-view change, determine which old and new CPU/GPU sensor series can be continued separately, plus an English gloss. The verb ('klären'/'Preserve... continuity') and resource (CPU/GPU sensor series) are explicit, though it does not distinguish itself from any sibling by name.

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 trigger context is given ('Nach Wechsel der Monitoring-Ansicht'), which tells the agent when the tool applies. There is no statement of when not to use it and no alternative tool is referenced, so the guidance stops at implied usage.

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