Skip to main content
Glama

getecoback-climate-weather

angebot_lagerstatus_zitieren

Read-only

Verfügbarkeit als datierte Händlerbeobachtung ausgeben — Qualify an availability quote by exact offer and observation date.

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": {
      "stand": "<stand>",
      "heute_geprueft": "<heute_geprueft>",
      "modell_und_haendler_geprueft": "<modell_und_haendler_geprueft>"
    },
    "name": "angebot_lagerstatus_zitieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
standYesBeobachtung des exakten Händlerangebots.
heute_geprueftYesWurde das Angebot heute erneut selbst aufgerufen?
modell_und_haendler_geprueftYesSind Variante und Händler eindeutig identifiziert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 by structured data. The description adds the meaningful nuance that the result is a dated, offer-bound snapshot rather than a live lookup, but it does not say whether the observation is persisted, how it is returned, or what happens if the booleans are false.

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 definition is short and front-loaded with the German statement of purpose. The English half largely restates the German half rather than adding new information, which is mild redundancy but not enough to hurt usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter, read-only tool with full schema documentation and no output schema, the description covers the gist but omits what the emitted observation actually looks like and what the qualification booleans gate. It is minimally adequate rather than complete.

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% with all three parameters described and one enum, so the schema carries the semantics. The description only loosely echoes the observation-date and exact-offer concepts ('datierte', 'exact offer') without adding format, default, or edge-case meaning beyond the schema — the 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?

The description gives a specific verb and resource: output availability as a dated dealer observation ('Verfügbarkeit als datierte Händlerbeobachtung ausgeben'). It is clearly distinguishable from the comparison/estimate siblings, but it never names or contrasts a specific alternative, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through 'Qualify an availability quote by exact offer and observation date' — an agent can infer this is for recording a checked availability status, but there is no explicit when-not guidance, no prerequisites, and no mention of sibling tools that compare or aggregate offers.

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