Skip to main content
Glama

getecoback-climate-weather

ersatzteil_angebotsalternativen_gemeinsames_lager

Read-only

Zwei konkrete lieferbar ausgewiesene Angebote auf denselben bestätigten Erfüllungsweg prüfen — Distinguish two seller listings from independently supported fulfillment.

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": {
      "a_bestandsaussage_bestaetigt": "<a_bestandsaussage_bestaetigt>",
      "b_bestandsaussage_bestaetigt": "<b_bestandsaussage_bestaetigt>",
      "lagerbezug": "<lagerbezug>"
    },
    "name": "ersatzteil_angebotsalternativen_gemeinsames_lager"
  }
}

Input Schema

NameRequiredDescriptionDefault
lagerbezugYesWie hängen die tatsächlich zuständigen Lagereigentümer für A und B laut Beleg zusammen?
a_bestandsaussage_bestaetigtYesSpezifisches Teil, Menge und Lagerangabe in Angebot A direkt bestätigt?
b_bestandsaussage_bestaetigtYesDasselbe für Angebot B?

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 covered. Beyond that the description adds almost nothing: it does not say whether the check is purely evaluative, what happens with the "offen" warehouse case, or what form the verdict takes. The one extra signal, that the tool is about distinguishing co-located from independently supported supply, is too compressed to act on.

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?

It is a single short sentence, so nothing is padded, but the brevity is achieved by compressing two ideas into an em-dash fragment rather than by front-loading a clear statement. The German and English halves partially duplicate each other instead of complementing each other.

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 three required inputs, no output schema, and a verification-style operation, the description should at minimum convey what the result represents and how to interpret a positive versus negative outcome. Neither is present, leaving the agent unable to predict the return value for a tool whose entire value is a judgment.

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% with three documented parameters and an enum on lagerbezug, so the schema carries parameter meaning on its own. The description does not reference any parameter, which is acceptable at this coverage level but adds no value. Baseline 3 applies.

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 a verb ("prüfen") and a resource (two offers marked as available on the same confirmed fulfillment path), and it gestures at the discriminating question: same fulfillment path versus independently supported fulfillment. However, it never says what the tool returns or what class of answer it produces, and the phrase "bestätigten Erfüllungsweg" is unexplained jargon. An agent can guess the topic but not the operation's output.

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 when-to-use or when-not-to-use guidance. Siblings such as angebot_lagerstatus_zitieren and angebote_gesamtpreis_vergleichen plausibly overlap in domain, yet the description never routes between them. The clause "Distinguish two seller listings from independently supported fulfillment" hints at a decision boundary but not at when an agent should call this tool.

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