Skip to main content
Glama

getecoback-climate-weather

venta_rollwagen_6060_url_und_6060500_artikel

Read-only

Trennt die Artikelnummer der ausgewählten Variante von der Gruppennummer im Webpfad — Distinguish the visible trolley SKU from the family URL component.

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": {
      "beleg": "<beleg>",
      "auswahl_abgeglichen": "<auswahl_abgeglichen>"
    },
    "name": "venta_rollwagen_6060_url_und_6060500_artikel"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegYesTatsächlich vorliegende Kennung.
auswahl_abgeglichenYesDie tatsächlich ausgewählte Shop-Variante und genau das Angebot wurden abgeglichen?

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 safety is covered. The description adds no behavior beyond the concept: it does not say what the call produces, how the 'auswahl_abgeglichen' flag changes the outcome, or what 'offen' means as a result, and there is no output schema to compensate.

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?

The description is short and front-loaded, but it spends half its length restating the same sentence in English after the German, which is redundancy rather than added information. Two clauses, one of them duplicated.

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 two required parameters, an enum of four identifier cases, and no output schema, the description should explain what the tool returns for each case and how the boolean gates the result. It does neither, leaving the agent unable to predict the outcome of a 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 description coverage is 100%, so both parameters are already documented in the schema; the description adds no syntax or interpretation beyond that. It also never mentions the required boolean 'auswahl_abgeglichen', so baseline 3 is the correct ceiling.

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 does state an operation ('Trennt ... von ...') on two named resources, the variant article number and the group number in the web path, so the general intent is inferable. However, the phrasing is abstract and restates the compound tool name rather than saying plainly that an ambiguous identifier is classified; it gives no contrast to any of the many similarly named 'rollwagen' siblings.

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 statement of when to call this tool versus the other rollwagen tools, and no prerequisite or exclusion is given. An agent must guess from the enum values (offen, andere_artikelnummer) that this is for resolving an unclear article/URL identifier.

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