Skip to main content
Glama

getecoback-climate-weather

stapelsaeule_auszugsnutzen_zwei_getrennte_arbeitsproben

Read-only

An einem zulässigen Vergleichsaufbau die wirkliche Zahl verbleibender externer Zwischenablagen vergleichen — Check whether a pull-out worktop actually replaces a separate staging step in your routine.

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": {
      "paar_vergleichbar": "<paar_vergleichbar>",
      "ohne_auszug_extern": "<ohne_auszug_extern>",
      "mit_auszug_extern": "<mit_auszug_extern>",
      "eigenes_ziel": "<eigenes_ziel>"
    },
    "name": "stapelsaeule_auszugsnutzen_zwei_getrennte_arbeitsproben"
  }
}

Input Schema

NameRequiredDescriptionDefault
eigenes_zielYesMindestens beobachtet zu ersetzende externe Ablagen für den eigenen Nutzen.
mit_auszug_externYesBei der Probe mit zulässiger leer gestarteter Arbeitsplatte weiterhin beobachtete externe Zwischenablagen.
paar_vergleichbarYesWaren benutzte Wäschemenge, Arbeitsschritt und beide zulässigen Vergleichsaufbauten nachvollziehbar gleichwertig?
ohne_auszug_externYesBei der Probe ohne lokale Arbeitsplatte beobachtete externe Zwischenablagen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare this as read-only and closed-world, so the safety profile is clear. The description adds that the comparison requires a valid setup, but it does not explain how the comparison is evaluated, what result is returned, or how a non-comparable setup 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?

The description is short and front-loads the comparison objective. The German and English sentences largely restate each other, which is slightly redundant, but the overall structure remains efficient.

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?

The input schema fully documents the four required parameters, and annotations cover the read-only nature of the tool. However, with no output schema, the description should explain what the comparison returns or how the result should be interpreted, and it does not.

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 all four parameters are already documented in the schema. The description reinforces that external staging areas are being compared and that the setup must be valid, but it adds no parameter-level meaning beyond what the schema already 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 comparison: it compares the number of remaining external staging areas with and without a pull-out worktop against the user's target. The English sentence makes the practical question explicit ('whether a pull-out worktop actually replaces a separate staging step'), so the purpose is understandable, though no sibling tool is named to differentiate it.

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?

Usage is implied by the phrase 'on a permissible comparison setup' and by the `paar_vergleichbar` parameter, which signals the comparison must be valid. However, the description does not explicitly say when to use this tool versus related sibling tools, nor does it state any exclusion conditions.

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