Skip to main content
Glama

getecoback-climate-weather

schublade_zugriff_hintere_tiefe

Read-only

Für häufig gebrauchte Teile die tatsächlich herausfahrende Tiefe des Auszugs berechnen — Find how much of a drawer stays behind the cabinet front.

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": {
      "innentiefe_cm": "<innentiefe_cm>",
      "freiliegend_cm": "<freiliegend_cm>",
      "teil_hinterkante_cm": "<teil_hinterkante_cm>"
    },
    "name": "schublade_zugriff_hintere_tiefe"
  }
}

Input Schema

NameRequiredDescriptionDefault
innentiefe_cmYesNutzbare Tiefe innen in der Schublade.
freiliegend_cmYesBei normaler Öffnung vor der Schrankkante frei sichtbare Tiefe.
teil_hinterkante_cmYesTiefe bis zur hinteren Kante des häufig gebrauchten Teils ab Schubladenvorderkante.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 agent knows this is a safe, closed-world computation with no side effects. The description confirms it is a calculation ("berechnen") rather than an action on a physical drawer, but it does not state what the returned value represents or how the result should be interpreted. With annotations carrying the safety profile, this is adequate but thin.

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?

The description is short and front-loaded, but it is essentially bilingual duplication: the German and English clauses express related but not clearly reconciled quantities. Both sentences earn some place, but the lack of a clear single framing makes the definition slightly harder to parse than necessary.

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?

This is a three-parameter calculation tool with full schema coverage and no output schema, so the description should ideally clarify what result is returned (remaining drawer depth versus protruding depth). It does not, leaving the output meaning ambiguous. The core context is present, but the definition is not fully complete for an agent to interpret the calculation confidently.

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 three parameters (innentiefe_cm, freiliegend_cm, teil_hinterkante_cm) are already documented in the schema. The description adds no parameter-level meaning, formulas, or units beyond what the schema provides. Baseline 3 is appropriate when the schema fully covers the inputs.

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 calculation ("die tatsächlich herausfahrende Tiefe des Auszugs berechnen") and a concrete resource, the drawer pull-out depth. The English gloss reframes it as "how much of a drawer stays behind the cabinet front," which is a related but not identical quantity; that slight internal mismatch keeps it from a 5. It does not explicitly differentiate itself from sibling drawer tools, but the purpose is clear enough to select 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?

The phrase "Für häufig gebrauchte Teile" gives an intended scenario for using the tool, which is useful context. However, there is no explicit when-not guidance, no mention of prerequisites, and no routing to alternative sibling tools for other drawer calculations. Usage is implied rather than fully specified.

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