Skip to main content
Glama

getecoback-climate-weather

kuechenablage_blech_quer_oder_laengs_probe

Read-only

Bei kalter Stellprobe entscheiden, ob ein vorhandenes Blech auf eine zuvor freigeräumte rechteckige Ablage passt — Compare both rectangular orientations for a cold baking tray.

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": {
      "frei_lang_cm": "<frei_lang_cm>",
      "frei_breit_cm": "<frei_breit_cm>",
      "blech_lang_cm": "<blech_lang_cm>",
      "blech_breit_cm": "<blech_breit_cm>",
      "stellplatz_bestaetigt": "<stellplatz_bestaetigt>"
    },
    "name": "kuechenablage_blech_quer_oder_laengs_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_lang_cmYesGemessene durchgehend freie Länge der bereits vorgesehenen Ablage.
blech_lang_cmYesAußenlänge des vorhandenen kalten Blechs einschließlich Seitenrändern.
frei_breit_cmYesGemessene durchgehend freie Breite derselben Ablage.
blech_breit_cmYesAußenbreite des Blechs einschließlich Griffen oder Rändern.
stellplatz_bestaetigtYesIst die Ablage für den vorgesehenen konkreten Zweck geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the bar is lower. The description adds useful context that this is a decision/comparison rather than a measurement, and that the shelf was cleared beforehand, but it does not say what verdict is produced (single boolean vs. per-orientation answer) or how a marginal case is handled.

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?

A single front-loaded sentence states the decision and the comparison, followed by a short English gloss. No filler, though the bilingual duplication means the English half mostly restates the German half rather than adding information.

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?

All five required parameters are fully described in the schema and the tool is read-only, so the core is adequate. The notable gap is the return value: with no output schema, the description should say whether the result is a yes/no fit or an orientation recommendation, and it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns more by explaining that the two length/width pairs are cross-compared in both orientations — meaning the numbers are compared as swapped pairs, not slot-by-slot. That is real semantic value beyond the field descriptions, which only define each measurement in isolation.

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 decision ('entscheiden, ob ein vorhandenes Blech ... passt') on a concrete resource (a previously cleared rectangular shelf), and adds the scope 'Compare both rectangular orientations'. It is distinguishable from measurement-style siblings such as backofen_blech_sichtprobe_mitte_und_rand by the explicit fit-decision framing, though no sibling is named.

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?

'Bei kalter Stellprobe' implies the when: a cold trial placement, not a hot/oven situation, which implicitly excludes the hot-tray sibling cases. However, no explicit alternative is named and there is no statement of when this tool should not be used (e.g. non-rectangular shelves), so the guidance is only implied.

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