Skip to main content
Glama

getecoback-climate-weather

schubladen_markierungen_zuordnen

Read-only

Bei ähnlich aussehenden Fächern fehlende Orientierungsmarken und die gemessene Beschriftungsbreite ermitteln — Plan how many distinct drawer labels are still needed and check the space for a tested label.

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": {
      "faecher_gesamt": "<faecher_gesamt>",
      "eindeutig_markiert": "<eindeutig_markiert>",
      "freie_frontbreite_cm": "<freie_frontbreite_cm>",
      "getestete_marke_breite_cm": "<getestete_marke_breite_cm>"
    },
    "name": "schubladen_markierungen_zuordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
faecher_gesamtYesAnzahl der häufig verwechselten Fächer.
eindeutig_markiertYesDavon in eigener Zugriffsprobe schon ohne Nachsehen eindeutig erkannt.
freie_frontbreite_cmYesKleinste freie Breite an der vorgesehenen Position auf den übrigen Fronten.
getestete_marke_breite_cmYesBreite der ausprobierten visuellen oder tastbaren Marke inklusive eigenem Randbedarf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 by structured data. The description adds the useful framing that the result is a planning/estimation quantity ('Plan how many ... are still needed'), but it never says what the tool actually returns (a count? a fit/no-fit verdict? both) and no output schema exists to fill that gap. With annotations carrying safety, a 3 is appropriate.

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 condition before the goal. However, it says essentially the same thing twice in German and then in English, which is a redundant restatement rather than added information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, fully documented, read-only computation tool, the description gives enough to know what question the tool answers. The one real gap is the absence of any hint about the result shape, which matters because there is no output schema; otherwise little is missing relative to the tool's complexity.

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 all four parameters carry their own German descriptions, including ranges, so the schema does the semantic work. The tool description adds no extra meaning about how 'eindeutig_markiert' relates to 'faecher_gesamt' or how the two width values are compared. Baseline 3 applies when the schema already documents every parameter.

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 concrete computation: determine how many distinct drawer labels are still missing and whether a tested label fits the available front width. The verb+resource is identifiable ('fehlende Orientierungsmarken ... ermitteln', 'Plan how many distinct drawer labels are still needed'). It does not name any sibling tool, so the agent gets no positive differentiation, only an implicit scope condition ('bei ähnlich aussehenden Fächern').

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?

There is a scope condition (identical-looking drawers) but no explicit when-to-use trigger, no when-not-to-use guidance, and no named alternative among the many sibling tools. The agent must infer from the drawer-label framing alone that this is the right tool for a labeling-feasibility question rather than, say, a measurement or lighting-topic tool.

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