Skip to main content
Glama

Dr. Dotzauer Calculators

kalorienverbrauch

Kalorienverbrauch EINER Sport-/Alltagsaktivität (MET-basiert: kcal = MET × kg × Stunden). Nicht der Gesamtumsatz, dafür grundumsatz/kaloriendefizit nutzen. Wie der Kalorienverbrauch-Rechner auf drdotzauer.de/kalorienverbrauch-rechner.

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": {
      "weight_kg": "<weight_kg>",
      "duration_min": "<duration_min>"
    },
    "name": "kalorienverbrauch"
  }
}

Input Schema

NameRequiredDescriptionDefault
metNoOptionaler MET-Wert, überschreibt activity
activityNoAktivität (setzt den MET-Wert); alternativ met direkt angeben
weight_kgYes
duration_minYesDauer in Minuten (1–600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses the actual computation (kcal = MET × kg × Stunden) and anchors behavior to a public reference calculator. It omits edge-case behavior for out-of-range duration or unknown activity and says nothing about result rounding, which keeps it below a 5.

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?

Three short sentences, scope and formula front-loaded, exclusions in the middle. The website reference is the only soft sentence, serving as a behavioral calibration anchor rather than filler.

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 four-parameter pure calculation with no output schema, the description supplies the formula so the agent can predict the return value, and the schema covers the enum list and met-override. Missing only error/validation behavior for out-of-range inputs (1–600 min is in the schema).

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 75% and the schema already documents met, activity and duration_min, so the baseline is 3. The formula in the description clarifies what weight_kg and duration_min are actually consumed by, adding modest value beyond the field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific computed quantity ('Kalorienverbrauch EINER Sport-/Alltagsaktivität') and its method (MET-basiert), and explicitly distinguishes it from the two sibling tools an agent might confuse it with (grundumsatz, kaloriendefizit). The uppercase 'EINER' reinforces the single-activity scope.

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

Usage Guidelines5/5

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

Gives an explicit negative condition ('Nicht der Gesamtumsatz') plus a named alternative route for that case ('dafür grundumsatz/kaloriendefizit nutzen'), which are both present in the sibling list. The agent can route between tools without opening a schema.

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