Skip to main content
Glama

getecoback-climate-weather

gebrauchtangebot_teilabholung_aufteilung_nach_beleg

Read-only

Ein zweigeteiltes Abholangebot auf ausstehende unersetzbare Teile begrenzen — Decide whether the first partial pickup covers a self-contained intended task.

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": {
      "beide_teilelisten_belegt": "<beide_teilelisten_belegt>",
      "direkt_notwendig": "<direkt_notwendig>",
      "erste_abholung": "<erste_abholung>",
      "in_zweiter": "<in_zweiter>",
      "zweite_auch_tatsaechlich_uebergeben": "<zweite_auch_tatsaechlich_uebergeben>"
    },
    "name": "gebrauchtangebot_teilabholung_aufteilung_nach_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_zweiterYesWeitere davon, die ausdrücklich erst in der zweiten Übergabe zugesagt sind.
erste_abholungYesDavon bereits bestätigt in der ersten Übergabe.
direkt_notwendigYesEinzeln erfasste Teile für die erste beabsichtigte Aufgabe.
beide_teilelisten_belegtYesSind beide Lieferumfänge und die zur ersten Aufgabe notwendigen Teile bestätigt?
zweite_auch_tatsaechlich_uebergebenYesSind die Teile der zweiten Übergabe bereits tatsächlich geprüft übergeben?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 covered. The description adds only that this is a decision/evaluation about partial pickup coverage, without explaining how the five inputs combine, what the output expresses, or any behavioral constraints. For a read-only decision tool with annotations already carrying the safety signal, this is minimal additional context.

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?

The description is a single, efficiently structured sentence pair that front-loads the scoping constraint before the decision question. There is no wasted wording, though the bilingual phrasing is slightly fragmented.

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?

For a five-parameter decision tool with no output schema, the description should clarify the decision logic, the meaning of the result, and how the parameters interact. It does not do so, leaving an agent with only a high-level framing. The rich schema mitigates this somewhat, but the overall definition remains incomplete for the tool's complexity.

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 documented in the schema itself. The description does not add meaning beyond what the schema provides for any individual parameter, which is the expected baseline when the schema does the heavy lifting.

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 states a specific decision task — whether a first partial pickup covers a self-contained intended task — and an overarching constraint about limiting a two-part pickup offer to outstanding irreplaceable parts. However, the phrasing is abstract and domain-specific, and it gives no indication of how this tool differs from the many similarly named sibling tools. The purpose is decipherable but not immediately clear.

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 frames the decision question the tool answers, but it offers no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer the usage context from the cryptic name and parameter set.

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