Skip to main content
Glama

getecoback-climate-weather

stapelsatz_ablagefunktion_gegen_nutzungszweck

Read-only

Eine gewünschte Zwischenablage zur Arbeitsplatte oder Stauraumschublade des konkreten Satzes abgleichen — Distinguish a pull-out worktop from storage when choosing a kit.

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": {
      "satz": "<satz>",
      "zweck": "<zweck>",
      "eigenes_getrenntes_moebel": "<eigenes_getrenntes_moebel>"
    },
    "name": "stapelsatz_ablagefunktion_gegen_nutzungszweck"
  }
}

Input Schema

NameRequiredDescriptionDefault
satzYesExakt bezeichneter Satz.
zweckYesEigene wesentliche Aufgabe.
eigenes_getrenntes_moebelYesWird derselbe Zweck durch ein tatsächlich nutzbares unabhängiges Möbel am Einsatzort abgedeckt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/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 no behavioral context beyond that — nothing about what the comparison returns, how the three inputs combine, or what happens with mismatched values. For a read-only lookup the bar is lower, but the description contributes essentially nothing behavioral.

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, but the German and English halves restate the same idea rather than front-loading a single clear purpose, and the German clause is grammatically tangled. No wasted length, but the structure does not aid quick comprehension.

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?

With three required, fully documented parameters, no output schema, and read-only annotations, the definition is minimally sufficient. The gaps are the ambiguous operation and the absence of any guidance on interpreting the boolean 'eigenes_getrenntes_moebel' in the decision, which the description never addresses.

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 both enums are documented, so the schema carries the parameter meaning. The description gestures at 'konkreten Satz' and the worktop/storage distinction, which loosely maps to 'satz' and 'zweck', but adds no syntax or interpretation beyond the schema. Baseline 3 applies.

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 verb 'abgleichen' (match/compare) and the objects 'Arbeitsplatte oder Stauraumschublade' and 'Nutzungszweck' give a rough sense of a comparison tool, and the English clause 'Distinguish a pull-out worktop from storage when choosing a kit' narrows it. However, the phrasing is awkward ('Zwischenablage' is an odd term for a tray) and the exact operation — matching a desired storage type against a kit's configuration — is only inferable, not stated cleanly.

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 English sentence implies the context (choosing a kit, deciding between pull-out worktop and storage), which is a usable when-to-use hint. But it names no alternatives, no exclusions, and no prerequisites, so the agent must infer when this tool is preferred over the many sibling comparison 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