Skip to main content
Glama

getecoback-climate-weather

mikrowelle_gefaessfreigabe_korpus_deckel_dekor_unterscheiden

Read-only

Die Herstellerfreigaben für Gefäß, Deckel und Dekor bei Mikrowellennutzung einzeln zusammentragen — Treat lid, decoration and vessel approval as separate operating evidence.

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": {
      "korpus": "<korpus>",
      "deckel": "<deckel>",
      "dekor": "<dekor>"
    },
    "name": "mikrowelle_gefaessfreigabe_korpus_deckel_dekor_unterscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
dekorYesMetallisches Dekor am konkret verwendeten Gefäß.
deckelYesGelesene Freigabe für den tatsächlich verwendeten Deckel.
korpusYesGelesene Herstellerfreigabe für den Gefäßkörper.

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. The description contributes the non-obvious behavioral constraint that each approval is independent evidence, but it says nothing about what is returned or how partial/unknown readings are handled.

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?

A single front-loaded German sentence with the guidance clause, followed by a short English gloss. The bilingual restatement is mildly redundant but the core instruction is clear and wastes little space.

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

Completeness4/5

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

For a read-only tool with three fully documented enum parameters and no output schema, the definition supplies enough context to call it correctly. The only gap is the absence of any statement about how unknown or missing approvals are represented in the result.

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% and all three parameters are enums with their own descriptions, so the schema carries the semantic load. The description reinforces the separateness of korpus/deckel/dekor but adds no syntax or value-level meaning beyond that, which matches the baseline 3.

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 concrete verb and resource set: collecting manufacturer approvals for vessel, lid and decoration for microwave use, and it specifies that the three must be gathered individually. That is clearly more than a restatement of the name, though it does not name a sibling to contrast with.

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?

'einzeln zusammentragen' and 'Treat ... as separate operating evidence' imply how the tool should be used — keep the three approvals distinct rather than merged. No explicit when-to-use condition or named alternative is given, so the guidance stays implicit.

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