Skip to main content
Glama

getecoback-raumklima

haendler_link_modellnachweis

Read-only

Suchtreffer, Produktseite und geprüftes Angebot auseinanderhalten — Identify what a merchant link establishes about the exact model.

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": {
      "linktyp": "<linktyp>",
      "varianten_id": "<varianten_id>",
      "verkaeufer": "<verkaeufer>"
    },
    "name": "haendler_link_modellnachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
linktypYesZiel des Links.
verkaeuferYesKonkretes Angebot samt Verkäufer sichtbar?
varianten_idYesGenaues Variantenkennzeichen auf der Händlerseite mit Quelle 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?

The annotations already establish that this is a read-only, non-open-world operation, so the description does not need to restate safety. It adds useful conceptual framing by identifying the three evidence levels, but it omits how ambiguous cases are handled and what the tool actually returns.

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 very short and front-loads the three evidence categories before the explanatory clause. It is efficient, though the bilingual fragments make it slightly less direct than a single clear sentence would be.

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?

The tool has only three parameters and no output schema, so the description carries more burden to explain the expected result. It gives conceptual context but does not say what the tool returns, such as a classification, verdict, or status, leaving a key gap for an agent trying to interpret the response.

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%, so the individual parameters are already documented. The description adds some meaning by introducing the three categories that likely correspond to combinations of linktyp, verkaeufer, and varianten_id, but it does not state the exact combination rules or map each category to its parameters.

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 specific discrimination between search hit, product page, and verified offer, and frames it around the exact model. However, the action remains abstract: 'auseinanderhalten' and 'Identify what a merchant link establishes' do not clearly state whether the tool classifies, validates, or returns a status.

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 explicit when-to-use guidance, no prerequisites, and no named alternatives. The scenario is implied by the phrase about distinguishing link types, but an agent must infer the conditions under which this tool is the right choice.

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