Skip to main content
Glama

getecoback-raumklima

pc_cpu_gpu_lastmix_zu_gepaarten_proben

Read-only

Vor einem CPU/GPU-Vergleich Läufe mit Wiederholung beider protokollierter Lastabschnitte von einseitigen Proben trennen — Select PC trials that repeat both recorded workload segments.

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": {
      "paare_gesamt": "<paare_gesamt>",
      "nur_cpu_passend": "<nur_cpu_passend>",
      "nur_gpu_passend": "<nur_gpu_passend>",
      "beide_geeignet": "<beide_geeignet>"
    },
    "name": "pc_cpu_gpu_lastmix_zu_gepaarten_proben"
  }
}

Input Schema

NameRequiredDescriptionDefault
paare_gesamtYesZahl aller geplanten Vergleichspaare derselben Geräte.
beide_geeignetYesWeitere Paare mit vergleichbarem CPU- und GPU-Abschnitt, auch nach Leistungsprotokoll.
nur_cpu_passendYesPaare mit geeignetem CPU-Abschnitt, aber ungeeignetem GPU-Abschnitt.
nur_gpu_passendYesAndere Paare mit passendem GPU-Abschnitt, aber ungeeignetem CPU-Abschnitt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 substantive inclusion criterion (only runs repeating both segments count), which is genuinely behavioral, but says nothing about what the call returns or how the supplied counts are consumed. That is a real gap for a tool with no output schema.

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?

Compact and front-loaded, with the precondition stated first. The German sentence is immediately restated in English, which is mild duplication, but it serves bilingual clarity rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the burden of explaining the return value, and it does not: an agent still cannot tell whether it gets a list of trials, a filtered set, or derived counts. The mismatch between the 'select trials' framing and the four required aggregate inputs is left unexplained.

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 all four numeric parameters carry their own German descriptions, so the schema does the heavy lifting. The description adds no meaning about how the counts relate to the selection or what values are expected, which is the baseline-3 case when coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete action: separating runs that repeat both recorded workload segments from one-sided samples ahead of a CPU/GPU comparison. But it frames the tool as selecting trials, while the schema requires four aggregate counts (paare_gesamt, nur_cpu_passend, nur_gpu_passend, beide_geeignet) as inputs, so an agent cannot tell whether the tool returns trials or tallies. It is specific in vocabulary but ambiguous about the actual operation.

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 "Vor einem CPU/GPU-Vergleich" gives a clear sequencing hint: run this before doing the CPU/GPU comparison. No sibling alternative is named and no exclusion conditions beyond "one-sided samples" are stated, leaving the agent to infer where this fits among the many other pc_* 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