Skip to main content
Glama

getecoback-raumklima

backofen_blech_sichtprobe_mitte_und_rand

Read-only

Zwei auf demselben Backblech dokumentierte Sichtproben auf ungleich verteilte Ergebnisse abgleichen — Compare center and edge outcome counts for a fixed tray placement.

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": {
      "mitte_geprueft": "<mitte_geprueft>",
      "rand_geprueft": "<rand_geprueft>",
      "mitte_ziel_aussehen": "<mitte_ziel_aussehen>",
      "rand_ziel_aussehen": "<rand_ziel_aussehen>"
    },
    "name": "backofen_blech_sichtprobe_mitte_und_rand"
  }
}

Input Schema

NameRequiredDescriptionDefault
rand_geprueftYesEntsprechende Stücke an den Randpositionen.
mitte_geprueftYesGleichartige Stücke an den mittleren Prüfpositionen.
rand_ziel_aussehenYesGeprüfte Randstücke mit demselben Merkmal.
mitte_ziel_aussehenYesGeprüfte mittlere Stücke mit dem vorher festgelegten sichtbaren Merkmal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety and scope are covered. The description adds the meaningful constraint that both counts share one tray placement, but says nothing about how the comparison is computed, whether zero 'geprueft' values are handled, or what the response contains.

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?

It is short and front-loaded, but the German and English sentences are near-duplicates, so half the text carries no new information. A single sentence stating verb, resource, and the shared-tray constraint would be tighter.

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, four-required-number tool with no output schema, the definition identifies the inputs' domain but never explains that the two count pairs are meant to be compared as proportions, nor what an agent should report back. Adequate to start a call, insufficient to interpret 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%, so the four numeric parameters are already documented and the baseline of 3 applies. The description only restates the center/edge split and does not clarify the distinction between 'geprueft' totals and 'ziel_aussehen' matching counts, which is the one piece of meaning the schema leaves implicit.

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 concrete verb (abgleichen/compare) and a concrete resource (center vs. edge Sichtproben counts on the same tray), and the phrase 'fixed tray placement' implicitly separates it from tray-change siblings such as backofen_blechwechsel_gleichwertige_messpaare. It stops short of saying what the comparison produces, so the agent knows the topic but not the result.

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

Usage Guidelines2/5

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

No explicit when-to-use, when-not-to-use, or named alternative is given. The only guidance is the embedded constraint that both observations come from the same tray, which an agent must infer from the German phrase 'auf demselben Backblech'.

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