Skip to main content
Glama

getecoback-climate-weather

bodenpflege_teilchen_auffangprobe

Read-only

Bei der Sichtprobe verschobene Teilchen von erfassten Teilchen trennen. — Separate visibly captured debris from debris displaced to the adjacent area.

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": {
      "teilchen_vorher": "<teilchen_vorher>",
      "im_behaelter": "<im_behaelter>",
      "im_nachbarabschnitt": "<im_nachbarabschnitt>",
      "im_testabschnitt": "<im_testabschnitt>"
    },
    "name": "bodenpflege_teilchen_auffangprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
im_behaelterYesDavon im Auffangbehälter sichtbar wiedergefundene Teilchen.
teilchen_vorherYesNatürlich vorhandene, sichtbare und für das Gerät geeignete Teilchen in einem abgegrenzten Abschnitt.
im_testabschnittYesDavon weiterhin sichtbar im ursprünglichen Abschnitt.
im_nachbarabschnittYesDavon nach dem Lauf sichtbar in angrenzende, zuvor freie Abschnitte verschobene Teilchen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 known. The description adds nothing beyond that: it does not say whether the four counts are reconciled arithmetically, whether an imbalance is flagged, or what quantity the agent should expect back. For a pure-calculation tool with no output schema, that is a real gap.

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?

Two short sentences, so nothing is bloated, but the German and English versions say slightly different things instead of one being a faithful rendering, which adds confusion rather than clarity. The text is not front-loaded with what the tool determines.

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?

A read-only tool whose whole purpose is to combine four particle counts, with no output schema, needs the description to state the computation and the result. Neither is present, so an agent knows the topic but not what invoking it produces or how to interpret the answer.

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 the four parameters are fully documented in the schema and the baseline is 3. The description's phrasing (separating displaced from captured particles) loosely maps onto the vorher/behaelter/nachbarabschnitt/testabschnitt split but adds no format, unit, or consistency rules beyond the schema.

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 description names an action ("verschobene Teilchen von erfassten Teilchen trennen") and the domain resource (Teilchen/debris), so the general subject is graspable. But it never says the tool performs a computation over the four counts, and it gives no differentiation from siblings such as bodenpflege_sichtspuren_trockenprobe or bodenpflege_referenzstellen_gegenprobe. "Separate" is also metaphorically vague about what the tool actually returns.

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?

No when-to-use statement, no preconditions, no mention of an alternative tool or of the relationship to the Sichtprobe/Trockenprobe siblings. An agent must infer from the name alone that this is the follow-up step after a visual debris inspection.

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