Commerce for Agents

Open Booking Form

start-booking

Read-onlyIdempotent

Opens the booking form for one offer from a comparison, identified by its ref; the form renders below the message. Read-only: the call submits, stores and sends nothing, and takes no personal data. In the form the user enters the contract details (page 1), then the IBAN and consent (page 2), and files the request there. Messages such as 'Bitte öffne das Buchungsformular', 'ich möchte diesen Tarif', 'den nehme ich', 'book #2' or 'switch me to this', usually sent by the card's 'Jetzt buchen' button, ask for this form. language sets the language of the form. There is no self-service checkout link. Keywords: Buchungsformular, Tarif buchen, wechseln, Wechsel beauftragen, Vertrag abschließen, open booking form, book, switch, sign up.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	Yes	Offer reference from a compare-tariffs result (field `ref`). No personal data.
`language`	No	Language of the conversation; the booking form uses it. Default: de.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ref`	Yes
`city`	No
`tariff`	Yes
`language`	Yes
`provider`	Yes
`energyType`	Yes
`postalCode`	Yes
`instruction`	Yes
`monthlyAvgEur`	Yes
`annualTotalEur`	Yes
`providerLogoUrl`	No
`annualConsumptionKwh`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

removedInput schema / properties / context

Removed value: -{
-  "description": "Why are you calling this tool? Briefly describe the user's goal.",
-  "type": "string"
-}

First observedSep 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this by stating it 'submits, stores and sends nothing, and takes no personal data'. It adds useful behavior beyond annotations: the form renders below the message, has a two-page flow, and there is no self-service checkout link.

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?

The description is front-loaded with the main action and read-only behavior, and the trigger examples are useful. The trailing keyword list is somewhat redundant, but overall each sentence earns its place.

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 rich annotations, full schema coverage, and presence of an output schema, the description covers the tool's purpose, side-effect profile, trigger phrases, form flow, language behavior, and absence of a checkout link. Nothing critical is missing for correct invocation.

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%, so the schema already documents both ref and language. The description adds only light reinforcement, noting ref identifies the offer and language controls the form language, but it does not materially extend the 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 states a specific verb and resource: it 'opens the booking form for one offer from a comparison, identified by its ref'. It also clarifies the tool is read-only and that the form renders below the message, which distinguishes it from siblings like book-contract or submit-switch-request.

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 gives strong when-to-use signals: example user messages ('book #2', 'switch me to this'), the card's 'Jetzt buchen' button, and the note that there is no self-service checkout link. It does not explicitly list alternative tools and when not to use them, but the usage context is clear.

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

All Commerce for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?