Skip to main content
Glama

getecoback-climate-weather

tado_x_funktionskosten_pruefen

Read-only

Zeitpläne und zusätzliche tado-X-Automationen beim Funktionsbudget unterscheiden — Identify possible recurring fees for the intended tado X app function.

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": {
      "funktion": "<funktion>",
      "jahrespreis_eur": "<jahrespreis_eur>",
      "preis_geprueft": "<preis_geprueft>",
      "jahre": "<jahre>"
    },
    "name": "tado_x_funktionskosten_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
jahreYesGeplanter Nutzungszeitraum in Jahren.
funktionYesGewünschte Funktion.
preis_geprueftYesIst der aktuelle Preis für genau die gewünschte Funktion bestätigt?
jahrespreis_eurYesAktuell selbst nachgesehener jährlicher Preis oder null Euro falls kostenfrei beziehungsweise unbekannt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 and the description is not obligated to restate it. It adds the behavioral nuance that the tool discriminates between function categories with respect to a budget, which is useful context beyond the annotations. It says nothing about what the check returns, how it treats unconfirmed prices, or what happens with the 'unbekannt' function.

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

Conciseness3/5

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

The definition is short, but it is effectively the same statement delivered twice — a German clause and an English clause that overlap rather than build on each other, so half the text is redundant for a monolingual reader. The scoping idea (distinguishing function types) is front-loaded, which is good, but the bilingual duplication costs it.

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 four-required-parameter read-only check with a fully documented schema, the description covers the intent adequately. The gap is that there is no output schema, so the agent has no idea what form the 'possible recurring fees' result takes or how the confirmed-price flag influences it.

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%, with every parameter documented including ranges and the enum, so the baseline is 3. The description adds only the framing of 'Funktionsbudget' and 'recurring fees', which loosely ties jahrespreis_eur and jahre together but does not explain the semantics of preis_geprueft or how jahre affects the verdict.

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 action (identify possible recurring fees) and a concrete object (the intended tado X app function), and the German clause specifies the scope as distinguishing schedules from additional automations within the function budget. That maps cleanly onto the enum values zeitplan / zusaetzliche_automatisierung, so the purpose is legible even without opening the schema. It does not differentiate itself from any sibling tool, which keeps it out of 5 territory.

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?

Usage is only implied: the agent can infer the tool is for cost/budget questions about a planned tado X app function, but the description never states when to call it versus not calling it, nor does it point to any alternative check. There are no stated prerequisites despite preis_geprueft being a required confirmation flag.

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