ecoExperten Energieausweis

bestellung_aufgeben

Verbrauchsausweis bestellen (59,00 EUR, Kauf auf Rechnung) — mit E-Mail-Bestätigung.

Legt eine schwebende Bestellung an und sendet einen Bestätigungslink an
die angegebene E-Mail-Adresse. Verbindlich (zahlungspflichtig) wird die
Bestellung erst, wenn der Empfänger den Link bestätigt; unbestätigte
Bestellungen verfallen nach 48 Stunden ohne Kosten. agb_akzeptiert und
zahlungspflichtig_bestaetigt geben die ausdrückliche Zustimmung des
Nutzers zu den AGB (ecoexperten.com/agb) und zur zahlungspflichtigen
Bestellung wieder; ohne beide Zustimmungen lehnt der Server die
Bestellung ab. Alle Angaben werden serverseitig gegen die GEG-Regeln
geprüft. test_modus=true simuliert die Bestellung, ohne sie anzulegen
und ohne E-Mail-Versand.

Input Schema

TableJSON Schema

Name	Required	Default
`ort`	Yes
`plz`	Yes
`email`	Yes
`keller`	No	Unbeheizt
`strasse`	Yes
`telefon`	No
`vorname`	Yes
`kuehlung`	No	Keine Kühlung
`lueftung`	No	Fensterlüftung
`nachname`	Yes
`test_modus`	No
`energy_unit`	Yes
`gebaeudetyp`	Yes
`has_vacancy`	No	Nein
`consumption_1`	Yes
`consumption_2`	Yes
`consumption_3`	Yes
`energy_source`	Yes
`agb_akzeptiert`	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
`doppelbestellung_bestaetigt`	No
`zahlungspflichtig_bestaetigt`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations like readOnlyHint=false, the description discloses substantial behavioral traits: the order is initially pending, a confirmation link is sent, it becomes binding only after recipient confirmation, unconfirmed orders expire after 48 hours at no cost, and both agb_akzeptiert and zahlungspflichtig_bestaetigt must be true. It also explains test_modus simulation and server-side GEG validation. No annotations are contradicted.

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?

The description is appropriately sized for a 37-parameter order tool. It is front-loaded with the headline summary, then uses short paragraphs for flow, consent, validation, and test mode. Every sentence adds value, with no redundancy or filler.

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?

Given the tool's complexity (37 params, 22 required) and the existing output schema, the description covers the essential operational context: price, payment method, pending/binding states, email confirmation, expiry, consent requirements, GEG validation, and test mode. This is sufficient for an agent to understand the tool's full lifecycle and invoke it responsibly.

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?

With 0% schema description coverage, the description compensates for the most semantically critical parameters: it explains that agb_akzeptiert and zahlungspflichtig_bestaetigt are required consents, without which the server rejects the order, and that test_modus=true simulates without side effects. However, it does not cover the many building/consumption parameters (e.g., energy_source, has_vacancy, consumption_1), leaving them to rely on their field names alone.

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 opens with 'Verbrauchsausweis bestellen (59,00 EUR, Kauf auf Rechnung) — mit E-Mail-Bestätigung', a clear verb+resource with price and payment method. The rest of the description details the order flow, making it unmistakable that this tool creates a pending order, distinct from siblings like bestell_status and bestellung_pruefen.

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 provides clear context for when to use it: to place a binding order after consent, with test-mode simulation available. It does not explicitly contrast with sibling tools or state 'don't use for status checks', but the context strongly implies this is the action tool for creating a new order.

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?