Skip to main content
Glama

getecoback-climate-weather

led_lebensdauer_l70b50_garantie_unterscheiden

Read-only

Eine L70/B50-Angabe, Schaltzyklen und schriftliche Garantie nach ihrer dokumentierten Aussage unterscheiden — Identify what a lifespan claim can support before relying on it for one lamp.

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": {
      "angabe": "<angabe>",
      "frage": "<frage>",
      "modell_bestaetigt": "<modell_bestaetigt>"
    },
    "name": "led_lebensdauer_l70b50_garantie_unterscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
frageYesWelcher Beleg wird für die aktuelle Entscheidung gesucht?
angabeYesTatsächlich dokumentierte Art der Angabe.
modell_bestaetigtYesIst die Angabe auf genau dieses Modell und die angegebenen Bedingungen bezogen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 structurally. The description adds the useful framing that this is an evidential assessment rather than a lookup, but with no output schema it never says what the result looks like (a verdict? a category? a caveat list?), which is the main behavioral gap.

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 short sentences, front-loaded with the distinguishing task and followed by the decision framing. The German/English doubling costs some space but keeps a single compact block with no filler.

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-parameter, all-required, read-only classification tool with no output schema, the description covers the intent but not the result contract or how the model-confirmation flag changes the conclusion. An agent knows why to call it but not what it will receive back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with enum descriptions, so the baseline is 3; however the description surfaces the same three claim categories that the 'angabe' and 'frage' enums encode, helping an agent map a real-world statement onto the right enum value. It does not mention 'modell_bestaetigt', a required boolean whose meaning for the outcome is left entirely to 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 names a specific verb (unterscheiden / distinguish) and three concrete claim types — L70/B50 statement, switching cycles, written warranty — and frames the outcome as 'what a lifespan claim can support'. That is far more specific than the name alone, though it does not differentiate itself from the many sibling *_unterscheiden tools by naming any of them.

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?

'before relying on it for one lamp' implies the moment of use: prior to trusting a lifespan figure for a specific fixture. There is no explicit when-not guidance and no named alternative or escalation path for cases that fall outside these three claim types.

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