ecoExperten Energieausweis

bestellung_pruefen

Read-only

Verbrauchsausweis-Bestellung vorprüfen (Pflichtfelder + GEG-Regeln), OHNE zu bestellen.

Gebäudedaten: gebaeudetyp (Einfamilienhaus/Zweifamilienhaus/Mehrfamilienhaus),
Adresse, Baujahre, anzahl_wohnungen, Wohnfläche in m².
Verbrauch: consumption_start = Beginn der ältesten von 3 Jahres-Abrechnungsperioden
(JJJJ-MM); consumption_1..3 = Jahresverbräuche in energy_unit (z. B. "kWh Brennwert");
hot_water_included = "Ja"/"Nein"/"Unsicher". Kostenlose Vorprüfung
ohne Bestellwirkung.

Input Schema

TableJSON Schema

Name	Required	Default
`ort`	Yes
`plz`	Yes
`keller`	No	Unbeheizt
`strasse`	Yes
`kuehlung`	No	Keine Kühlung
`lueftung`	No	Fensterlüftung
`energy_unit`	Yes
`gebaeudetyp`	Yes
`has_vacancy`	No	Nein
`consumption_1`	Yes
`consumption_2`	Yes
`consumption_3`	Yes
`energy_source`	Yes
`anzahl_wohnungen`	Yes
`baujahr_gebaeude`	Yes
`has_improvements`	No	Nein
`consumption_start`	Yes
`nutzt_erneuerbare`	No	Nein
`vacancy_percent_1`	No
`vacancy_percent_2`	No
`vacancy_percent_3`	No
`anlass_ausstellung`	No	Vermietung
`has_second_heating`	No	Nein
`hot_water_included`	Yes
`energetisch_saniert`	No	Nein
`baujahr_waermeerzeuger`	Yes
`energietraeger_heizung`	Yes
`gebaeudenutzflaeche_m2`	Yes
`energietraeger_warmwasser`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the agent knows it's read-only. The description adds that it's a pre-check (Vorprüfung) and is kostenlos (free). No contradiction. It could mention validation results behavior, but overall it adds meaningful context.

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 description is one paragraph with bullet-like lists. It is fairly concise but uses some abbreviations and German terms that may make it less clear. Could be more structured and readable.

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?

Given the high parameter count (29) and complexity, the description gives a high-level overview but lacks details on validation rules, handling of optional fields, and what the output looks like (though output schema exists). It is adequate but not fully complete.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only explains a subset of parameters (gebaeudetyp, Adresse, etc.). Many parameters like keller, kuehlung, lueftung are not described. The description does not compensate for the lack of schema descriptions on many fields.

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 'Verbrauchsausweis-Bestellung vorprüfen' which means pre-check an order for an energy consumption certificate, and emphasizes 'OHNE zu bestellen' (without ordering). It lists key fields, making the purpose very specific. It distinguishes itself from siblings like 'bestellung_aufgeben' (which places the order).

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 description says 'Vorprüfung ohne Bestellwirkung', indicating it is a validation step. It implies usage before ordering, but does not explicitly state 'when to use' vs. alternatives like 'bestellung_aufgeben'. Still, the context is clear enough.

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

All ecoExperten Energieausweis tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct stage of the ordering process: product info, pre-check, placing an order, and checking order status. There is no overlap between their responsibilities, and the descriptions clearly separate them.

Naming Consistency4/5

All tool names are in German snake_case, but the pattern is not fully uniform: two are noun-based (bestell_status, energieausweis_info) and two are verb-phrase-based (bestellung_aufgeben, bestellung_pruefen). The root word also varies slightly (bestell vs. bestellung), though the overall style is predictable and readable.

Tool Count5/5

Four tools is well-scoped for the server's purpose of handling an energy certificate order. Each tool covers a necessary step without redundancy or unnecessary additions.

Completeness5/5

The tool set covers the complete customer journey: information, pre-check, order placement, and status inquiry. There are no obvious gaps for the stated domain of ordering a Verbrauchsausweis.

Resources

Need Help?