Skip to main content
Glama
volsch

md24de-mcp

by volsch

get_consumption_report

Retrieve heating and hot-water consumption data for your property from messdienst24.de. Includes monthly usage, comparisons with average and previous periods, and historical trends.

Instructions

Return the heating and hot-water consumption report from messdienst24.de.

messdienst24.de is a German utility-consumption portal. This tool retrieves the full structured consumption data for your residential property. The report covers the most recently published month (returned as year/month at the top level) and also includes a history of several previous months so that trends can be analysed.

The response includes: year, month: The current reporting period (e.g. year=2025, month=4 for April 2025). object_info: Property address and object number assigned by the service provider. heating: Heating consumption data (see below). hot_water: Hot-water consumption data (same structure as heating).

Each meter section (heating / hot_water) contains: your_kwh: Your consumption for the current reporting month in kWh equivalent. average_kwh: Average consumption of comparable households in kWh equivalent. vs_average: How your usage compares to similar households this month. "less" = you used less, "more" = you used more, "equal" = same. null if the comparison is unavailable. vs_previous_month: How your usage compares to the previous month (same values). null if unavailable. vs_previous_year: How your usage compares to the same month last year (same values). null if unavailable. history: List of monthly readings for several past months, newest first. Each entry has year, month, your_kwh, average_kwh. history[0] always corresponds to the current reporting month.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. It details response structure and null handling. However, it does not explicitly state it is read-only or mention authentication or rate limits.

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?

Well-structured with bullet points and front-loaded purpose. Slightly verbose given an output schema exists, but every sentence adds value.

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

Completeness5/5

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

Complete for a no-parameter tool with output schema. Covers purpose, data source, response structure, and null handling. No missing essential information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. The description adds meaning by explaining the output structure in detail, which enriches understanding beyond the empty schema.

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?

The description clearly states the tool returns a heating and hot-water consumption report from messdienst24.de. It specifies the resource and distinguishes from siblings like get_last_available_month and save_pdf.

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 implied but not explicit. No instructions on when to use this vs alternatives or when not to use it. Siblings suggest differentiation but are not referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/volsch/md24de-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server