Skip to main content
Glama

getecoback-climate-weather

ersatzteil_angebotskanal_lagerstatus_timestamp

Read-only

Einen aktuellen belegten Lieferhinweis von datierten Katalog- und Marktplatzaussagen trennen — Check stale listing evidence without treating absent stock proof as out of stock.

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": {
      "aktuell_am": "<aktuell_am>",
      "status_am": "<status_am>",
      "quelle": "<quelle>",
      "max_alter_tage": "<max_alter_tage>",
      "teil_und_anbieter_geprueft": "<teil_und_anbieter_geprueft>"
    },
    "name": "ersatzteil_angebotskanal_lagerstatus_timestamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelleYesArt der vorliegenden Aussage.
status_amYesTag der Anbieterbestätigung für das exakte Teil. Datum YYYY-MM-DD, leer wenn unbekannt.
aktuell_amYesTag der Prüfung. Datum YYYY-MM-DD, leer wenn unbekannt.
max_alter_tageYesSelbst gewähltes Höchstalter des Belegs als Plausibilitätsfilter.
teil_und_anbieter_geprueftYesExakte Servicenummer einschließlich Variante sowie der tatsächliche Anbieter wurden abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 one genuinely useful behavioral rule: stale or dated catalog/marketplace claims must not be conflated with a negative stock verdict. It says nothing about what the check returns, how max_alter_tage affects the verdict, or what happens when status_am is empty/unknown.

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 clauses with no filler, and the operative constraint is front-loaded after the dash. The German half is denser than it needs to be, but nothing is redundant or padded.

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 five required parameters, no output schema, and a judgment-style operation, the description should say what comes back (a freshness verdict, a boolean, a classification?) and how unknowns are handled. Neither is stated, leaving the agent unable to predict the result shape or the effect of max_alter_tage, which is a substantive gap for this 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% with all five required parameters, the enum for quelle, and YYYY-MM-DD formats documented inline, so the schema carries the load. The description adds no parameter-level meaning beyond that, which places it at the baseline 3.

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 English clause ('Check stale listing evidence without treating absent stock proof as out of stock') comes closest to a verb+resource, but the German clause is abstract noun-stacking ('einen aktuellen belegten Lieferhinweis von datierten Katalog- und Marktplatzaussagen trennen') that never states plainly what gets computed. It also gives no differentiation from near-siblings such as angebot_lagerstatus_zitieren or ersatzteil_angebotsalternativen_gemeinsames_lager, so the agent must guess which freshness/stock tool applies.

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 and no named alternative. The only guidance-like content is a semantic guardrail ('do not treat absent stock proof as out of stock'), which shapes interpretation but does not tell the agent when to pick this tool over its many ersatzteil/angebot siblings.

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