Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_rueckgabe_vorentscheidung_claim_klaeren

Read-only

Anbieterhinweise zur Rückgabe und individuell bestätigte Bedingungen vor Zusage getrennt festhalten — Compare seller headline and actual written return terms.

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": {
      "rueckgabe_beworben": "<rueckgabe_beworben>",
      "frist_exemplar": "<frist_exemplar>",
      "zustandsbedingungen_klar": "<zustandsbedingungen_klar>",
      "rueckgabeweg_klar": "<rueckgabeweg_klar>"
    },
    "name": "gebrauchtgeraet_rueckgabe_vorentscheidung_claim_klaeren"
  }
}

Input Schema

NameRequiredDescriptionDefault
frist_exemplarYesLiegt eine konkrete schriftliche Frist für genau dieses Angebot vor?
rueckgabeweg_klarYesIst der tatsächlich akzeptierte Rückgabeweg angegeben?
rueckgabe_beworbenYesWird in der Angebotsübersicht allgemein Rückgabe genannt?
zustandsbedingungen_klarYesSind Bedingungen für Zustand und Vollständigkeit des Exemplars eindeutig angegeben?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read operation. The description adds the pre-commitment timing and the idea of separating advertised from confirmed terms, but it does not explain the return behavior or what the tool produces after comparing the booleans.

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 description is compact: one German sentence plus a short English comparison phrase. It front-loads the purpose and avoids unnecessary detail, though the bilingual presentation is slightly awkward.

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?

The four required booleans are well documented in the schema, and the description conveys the comparison context. But with no output schema, the description should explain what the tool returns or how the comparison result is expressed; that information is missing.

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%, and each boolean parameter already has a detailed German description in the schema. The tool description only alludes generally to return notes and confirmed conditions, adding no extra meaning or formatting guidance beyond the schema.

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 states a specific comparison task: seller headline versus actual written return terms, and says these should be kept separate before commitment. It is clear enough to distinguish from sibling tools focused on device condition, though the bilingual phrasing and domain jargon make it slightly less crisp than it could be.

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?

The phrase 'vor Zusage' implies the tool should be used before making a commitment, which gives useful timing context. However, the description does not explicitly state when not to use it or name a concrete alternative sibling 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