Skip to main content
Glama

getecoback-raumklima

poolroboter_korb_blaetter_feinreste_einordnung

Read-only

Korbaufnahme von Blättern und sichtbarem Feinmaterial getrennt protokollieren — Compare visible matter categories without treating basket contents as water quality.

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": {
      "blatt_a_g": "<blatt_a_g>",
      "blatt_b_g": "<blatt_b_g>",
      "fein_a_g": "<fein_a_g>",
      "fein_b_g": "<fein_b_g>",
      "gleiche_verfahren": "<gleiche_verfahren>"
    },
    "name": "poolroboter_korb_blaetter_feinreste_einordnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
fein_a_gYesSeparat erfasste Masse des sichtbaren Feinmaterials in A.
fein_b_gYesEntsprechende separat erfasste Masse in B.
blatt_a_gYesGemessene Blattmasse mit gleichem Abtropfverfahren in Lauf A.
blatt_b_gYesEntsprechende Blattmasse in Lauf B.
gleiche_verfahrenYesWaren Korb, Abtropfverfahren, Beobachtungsumfang und Arbeitsbereich vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare a read-only, closed-world operation, and the description adds a useful interpretive constraint: basket contents must not be treated as water quality. It still does not describe the output, how the comparison is evaluated, or what the 'Einordnung' result represents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is compact and front-loaded, with the core recording action followed immediately by the important interpretive caveat. No sentence is wasted.

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 description covers the input concepts and a key domain caveat, but for a five-parameter comparison tool with no output schema it does not explain what result the agent should expect. The required parameters are fully documented by the schema, so the main remaining gap is outcome clarity.

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 five parameters are already documented in the input schema. The description only restates the leaf-versus-fine-material distinction and adds no additional syntax, units, or comparison logic beyond the schema.

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 action — separately recording basket contents of leaves and visible fine material — and adds that the categories are compared. It does not explicitly distinguish itself from sibling pool-robot tools, so it is clear but lacks named differentiation.

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 through 'Compare visible matter categories' and the exclusion 'without treating basket contents as water quality'. However, there is no explicit statement of when to use this tool instead of related pool-robot 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