Skip to main content
Glama

getecoback-raumklima

gebrauchtgeraet_nutzungsprofil_alter_vs_umfang

Read-only

Zwei angebotene Geräte nur bei vergleichbar gezählten Gebrauchsanteilen auf Monatsraten vergleichen — Separate calendar age from observed use intensity.

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": {
      "gleiche_erfassung": "<gleiche_erfassung>",
      "a_monate": "<a_monate>",
      "a_einsaetze": "<a_einsaetze>",
      "b_monate": "<b_monate>",
      "b_einsaetze": "<b_einsaetze>"
    },
    "name": "gebrauchtgeraet_nutzungsprofil_alter_vs_umfang"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_monateYesVollständig belegte Monate von A.
b_monateYesVollständig belegte Monate von B.
a_einsaetzeYesDarin einzeln protokollierte Einsätze von A.
b_einsaetzeYesDarin einzeln protokollierte Einsätze von B.
gleiche_erfassungYesSind die beiden bekannten Zeiträume lückenlos und dieselben Einsatzarten erfasst?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the read-only, closed-world annotations, the description adds monthly normalization and a comparability guard. However, it does not explain the calculation or decision logic, the result form, or how the tool behaves when the recording periods are incomplete or capture different usage types.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses convey the task, its precondition, and the conceptual distinction between age and use intensity. The English clause adds clarification rather than merely translating the German, and there is 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?

The rich input schema and annotations make a basic invocation feasible, but there is no output schema and the description does not say whether the tool returns rates, a comparative judgment, or a refusal to compare. The unspecified false-comparability path is a material gap for this analytic tool.

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 already 100%, but the description adds useful relational meaning: the month and deployment pairs support monthly-rate normalization, while equivalent recording is necessary for a meaningful comparison. This goes beyond the individual field definitions without repeating their bounds or formats.

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 clearly identifies the resource and task: comparing two offered used devices through monthly rates while separating calendar age from observed use intensity. It does not explicitly distinguish itself from nearby usage-log or runtime siblings, and “compare” leaves the exact assessment product unstated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase “nur bei vergleichbar gezählten Gebrauchsanteilen” supplies an explicit precondition: monthly-rate comparison is appropriate only when usage was counted comparably. It gives no alternative for incomparable records and does not clarify whether gleiche_erfassung=false is a valid call that produces a non-comparability result.

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