Skip to main content
Glama

getecoback-climate-weather

spuelgang_verdeckte_innenflaechen_probe

Read-only

Sichtbare Speisereste in zuvor verdeckten und frei angeordneten gleichen Teilen vergleichen. — Compare visible residue on previously nested versus unobstructed pieces.

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": {
      "verdeckte_teile": "<verdeckte_teile>",
      "freie_teile": "<freie_teile>",
      "verdeckte_mit_resten": "<verdeckte_mit_resten>",
      "freie_mit_resten": "<freie_mit_resten>"
    },
    "name": "spuelgang_verdeckte_innenflaechen_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
freie_teileYesKontrollierte gleiche Teile mit frei erreichbarer Innenfläche.
verdeckte_teileYesKontrollierte gleiche Teile mit im Lauf teilweise verdeckter Innenfläche.
freie_mit_restenYesFrei angeordnete Teile mit sichtbaren Resten nach dem Lauf.
verdeckte_mit_restenYesVerdeckte Teile mit sichtbaren Resten nach dem Lauf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety is covered. The description adds no information about what the tool actually computes from the four counts, whether it returns a ratio/difference or how the two groups are compared. For a computation tool with no output schema, that silence leaves 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.

Conciseness4/5

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

Two compact sentences, the purpose stated up front with no filler. The German and English are direct translations of each other, which is mildly redundant but not harmful.

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?

With four required numeric parameters and no output schema, the description should explain what the comparison yields and how the inputs must be paired. It states only the subject matter, leaving the agent to guess at the returned value and whether the two group sizes must match.

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 each of the four counts is already documented in the schema and baseline 3 applies. The description's phrasing ("previously nested" vs "unobstructed", "visible residue") echoes the schema meanings without adding format, bounds, or edge-case guidance.

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 pairs a specific verb ("compare") with a specific subject (visible residue on previously nested versus unobstructed identical pieces), so an agent can tell this is a pair-comparison probe rather than a single-group count. It does not mention any sibling tool, so differentiation from the other spuelgang_* probes is left implicit.

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 no explicit statement of when to use this tool versus the many sibling spuelgang probes, and no prerequisites or exclusions are given. The agent must infer the use case (a dishwashing test comparing residue on shielded vs exposed surfaces) from the wording alone.

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