Skip to main content
Glama

getecoback-climate-weather

backofen_blechwechsel_gleichwertige_messpaare

Read-only

Beim Wechsel zwischen zwei zugelassenen Blechen vergleichbare Proben anhand dokumentierter Belegung trennen — Identify admissible measurements when tray shape or loading changed.

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": {
      "probepaare": "<probepaare>",
      "gleiche_belegung": "<gleiche_belegung>",
      "abweichende_blechposition": "<abweichende_blechposition>",
      "anderes_blech_wie_geplant": "<anderes_blech_wie_geplant>"
    },
    "name": "backofen_blechwechsel_gleichwertige_messpaare"
  }
}

Input Schema

NameRequiredDescriptionDefault
probepaareYesBeobachtete Versuchspaare für denselben Zweck.
gleiche_belegungYesPaare mit gleichartiger Belegung, Menge und demselben Programm.
abweichende_blechpositionYesDavon Paare mit abweichender Einschubhöhe, obwohl nur das Blech verglichen werden sollte.
anderes_blech_wie_geplantYesDavon abweichende Bleche am ursprünglich vorgesehenen Platz und mit vollständiger Beobachtung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this is a read-only, closed-world operation. The description adds that candidates are separated using documented occupancy and that admissibility depends on tray shape or loading changes, but it does not explain the decision rule, output form, or edge cases. With annotations covering safety, this is adequate but not rich.

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?

The definition is a single front-loaded sentence with a bilingual restatement. It contains no filler, though the German/English duplication is slightly redundant.

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 read-only analysis tool with four fully documented inputs, the description gives enough purpose and usage context. However, with no output schema it does not describe what the tool returns—such as filtered pairs, counts, or a verdict—or how admissible measurements are reported, leaving a meaningful gap.

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 all four numeric inputs are documented in the schema. The description does not add parameter-specific meaning or clarify how counts such as probepaare versus gleiche_belegung relate. Baseline 3 applies.

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—separating comparable samples and identifying admissible measurements—and gives the resource context of switching between two approved trays with changed tray shape or loading. It is clear, but it does not explicitly differentiate this tool from any sibling or name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context: during a change between two approved trays, especially when tray shape or loading has changed. It does not state when not to use it or point to an alternative, so it falls short of full guidance.

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