Skip to main content
Glama

getecoback-climate-weather

roboter_eingriffsbudget_serienprobe

Read-only

Drei aufeinanderfolgende beobachtete Roboterläufe gegen das eigene Eingriffsbudget prüfen. — Check three consecutive robot runs against a personal intervention budget.

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": {
      "eingriffe_lauf_eins": "<eingriffe_lauf_eins>",
      "eingriffe_lauf_zwei": "<eingriffe_lauf_zwei>",
      "eingriffe_lauf_drei": "<eingriffe_lauf_drei>",
      "maximal_je_lauf": "<maximal_je_lauf>"
    },
    "name": "roboter_eingriffsbudget_serienprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
maximal_je_laufYesFür die Alltagsroutine akzeptierte Eingriffe pro Lauf.
eingriffe_lauf_dreiYesManuelle Eingriffe in Lauf drei.
eingriffe_lauf_einsYesManuelle Eingriffe in Lauf eins.
eingriffe_lauf_zweiYesManuelle Eingriffe in Lauf zwei.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 comparison is against a 'personal' budget over exactly three consecutive runs, which is real behavioral context. However, it does not say what a failed check implies or whether a verdict/annotation is produced, and with no output schema that gap matters.

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 short sentences, front-loaded with the action and scope, with no filler. The German and English sentences duplicate the same content, which is mild redundancy but keeps the definition compact.

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 no output schema and four required parameters, so the description carries the burden of explaining what the check returns (per-run verdicts, an aggregate pass/fail, or the overage). None of that is present, leaving the agent unable to predict the result of the call.

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 coverage is 100%, so all four numeric parameters (three run counts plus the per-run maximum) are already documented in the schema. The description adds the notion that run one, two and three must be consecutive, but nothing about units, ordering constraints, or the relationship between the counts and the maximum beyond what the schema states. Baseline 3 applies.

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?

States a specific verb and resource: check three consecutive observed robot runs against an intervention budget. The 'three consecutive runs' scope distinguishes it from the sibling robot tools, which address other concerns. It stops short of a 5 because the nature of the 'check' (pass/fail per run, aggregate verdict) is not stated.

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 or when-not-to-use guidance and no alternatives named. The word 'personal' hints at a per-user budget, but there is no guidance on prerequisites, how a budget is established, or when another robot tool would be the right choice instead.

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