Skip to main content
Glama

getecoback-climate-weather

ersatzteil_teilerfolg_vor_komplettmeldung

Read-only

Trenne die dokumentierte Montage eines Ersatzteils vom wiederhergestellten Gebrauch — Separate proof of part installation from restored operation

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": {
      "genaue_teilenummer": "<genaue_teilenummer>",
      "montage_notiert": "<montage_notiert>",
      "beobachtung_vorher": "<beobachtung_vorher>",
      "vergleichbarer_nachtest": "<vergleichbarer_nachtest>"
    },
    "name": "ersatzteil_teilerfolg_vor_komplettmeldung"
  }
}

Input Schema

NameRequiredDescriptionDefault
montage_notiertYesEinbau des passenden Teils im Protokoll notiert
beobachtung_vorherYesBisheriger beobachteter Zustand
genaue_teilenummerYesErsatzteil ist über die Herstellerunterlage dem Gerät zugeordnet
vergleichbarer_nachtestYesFunktion nach Einbau im gleichen vorgesehenen Modus

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the conceptual split between installation proof and restored operation, but does not explain how the four inputs are evaluated, what conclusion is returned, or how conflicting evidence is 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?

The description is short and front-loads the core distinction. The bilingual repetition is somewhat redundant, but it remains compact and readable.

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?

For a four-parameter decision-support tool with no output schema, the description is too thin. It does not explain how the boolean and enum inputs combine into a separation judgment or what the caller should expect to receive.

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 all four parameters are already documented in the input schema. The description does not add meaning beyond the schema, which is acceptable at baseline 3 when the schema carries parameter semantics.

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 operation: separating documented spare-part installation from restored operation. It is more than a tautology and gives a usable conceptual distinction, though it does not clarify the 'partial success before complete report' framing from the tool name or differentiate it from 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 explicit guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The implied use case is evaluating partial evidence of a repair, but the agent must infer that entirely from the name and description.

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