Skip to main content
Glama

getecoback-raumklima

putztuecher_feste_zonen_markierung

Read-only

Markierte Reinigungstücher getrennten Bereichen zuordnen und den Vorratsengpass finden — Check dedicated labeled cleaning-cloth stock and reserve unassigned spares.

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": {
      "a_gekennzeichnet": "<a_gekennzeichnet>",
      "b_gekennzeichnet": "<b_gekennzeichnet>",
      "frei": "<frei>",
      "bedarf_a": "<bedarf_a>",
      "bedarf_b": "<bedarf_b>",
      "prioritaet": "<prioritaet>"
    },
    "name": "putztuecher_feste_zonen_markierung"
  }
}

Input Schema

NameRequiredDescriptionDefault
freiYesSaubere und für beide Bereiche ausdrücklich geeignete, noch nicht zugewiesene Tücher.
bedarf_aYesGeplanter Bedarf in A.
bedarf_bYesGeplanter Bedarf in B.
prioritaetYesBei Engpass zuerst auffüllen.
a_gekennzeichnetYesBereich A zugewiesene saubere Tücher.
b_gekennzeichnetYesBereich B zugewiesene saubere Tücher.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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. The description adds that the tool checks stock and finds a bottleneck, which is useful context, but it does not explain how the priority parameter affects the result or what the tool returns. It does not contradict the read-only annotation, since 'assign' can be interpreted as a computed allocation.

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 but repeats the same idea in German and English, which is redundant for an agent. The core purpose is front-loaded, but the bilingual duplication and the vague word 'reserve' reduce efficiency.

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

Completeness2/5

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

The tool has six required parameters and no output schema, so the description should explain what result to expect (for example, an allocation plan or a shortage indicator). Instead, it only describes the high-level goal and omits how the computed outcome is shaped by priority or free stock. This leaves a meaningful gap for an agent trying to interpret the tool's response.

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 six parameters are already documented in the input schema. The description does not add meaning beyond the schema for any parameter, such as how 'frei' interacts with demand or how 'prioritaet' changes the allocation. Baseline 3 is appropriate when the schema carries parameter documentation.

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 verb and resource: assign labeled cleaning cloths to separate areas and find the stock bottleneck. It is clear enough to distinguish from unrelated siblings. The bilingual restatement and the ambiguous term 'reserve' add slight noise but do not obscure the core purpose.

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?

The description states what the tool does but gives no explicit when-to-use or when-not-to-use guidance, and it does not mention any alternative tool or scenario. An agent must infer that this tool applies whenever cloth allocation or shortage analysis is needed.

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