Skip to main content
Glama

getecoback-climate-weather

pc_thermik_bildrate_und_aufloesung_abgleich

Read-only

In einer PC-Beobachtung Messpaare mit geändertem Ausgabeziel vor und nach einem Leistungsabfall aussortieren — Keep changed display-output settings out of matched thermal-performance observations.

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": {
      "abschnitte": "<abschnitte>",
      "aufloesung_geaendert": "<aufloesung_geaendert>",
      "rahmenlimit_geaendert": "<rahmenlimit_geaendert>",
      "belastung_offen": "<belastung_offen>"
    },
    "name": "pc_thermik_bildrate_und_aufloesung_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
abschnitteYesVorbereitete zeitlich gepaarte Temperatur- und Aufgabenabschnitte.
belastung_offenYesWeitere Abschnitte ohne ausreichenden Nachweis vergleichbarer Aufgabenlast.
aufloesung_geaendertYesDavon Abschnitte mit geänderter protokollierter Ausgabeauflösung.
rahmenlimit_geaendertYesWeitere Abschnitte mit geändertem ausdrücklich protokolliertem Bildratenlimit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/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 useful behavioral context by saying the tool excludes changed display-output settings and sections lacking comparable workload evidence, which is consistent with a read-only filtering operation; it does not describe the return shape, but that is a minor gap for a read-only tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense bilingual sentence, with the German and English versions largely duplicating each other. It is front-loaded and not excessively long, but the duplication and compound phrasing reduce efficiency.

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?

Inputs are fully covered by the schema and annotations establish a safe read-only profile. However, with no output schema, the description does not clarify what the tool returns after sorting out the affected measurement pairs, leaving a meaningful gap for a filtering tool with four required numeric inputs.

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 the four numeric parameters are already well documented in the schema. The description conceptually groups the exclusion criteria (resolution change, frame-limit change, open load) but adds no syntax, range, or interaction details beyond what the schema provides.

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 states a specific verb and resource: it sorts out ('aussortieren') matched measurement pairs with changed display-output settings in a PC observation before and after a performance drop. That is a clear, domain-specific purpose, though it does not explicitly distinguish itself from any sibling tool.

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 phrase 'In einer PC-Beobachtung ... vor und nach einem Leistungsabfall' implies the usage context, but there is no explicit when-to-use versus when-not-to-use guidance and no named alternative among the many sibling tools.

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