Skip to main content
Glama

Submit an ENQUIRY to Wärmepumpe Kosten Europa (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Wärmepumpe Kosten Europa: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before the Wärmepumpe Kosten Europa team sees it. Consent means the person has read and agreed to: "Diese Seite erhebt nichts und enthält kein Formular."

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": {
      "answers": "<answers>",
      "consent": "<consent>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Diese Seite erhebt nichts und enthält kein Formular.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does much of it: it discloses that step 1 only validates and returns a token, that step 2 is the actual submission, and that a confirmation email with a click-through gate precedes any team visibility — non-obvious behavior an agent could not guess. It stops short of failure modes: no mention of what happens with an invalid/expired token, a rejected answer set, or a repeat call to step 1.

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 front-loaded — the not-a-purchase disclaimer and the step framing come before detail, and the Step 1 / Step 2 structure mirrors the call sequence. It loses a point for restating the full consent sentence that already appears verbatim in the schema's consent property description.

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?

For a nested-object, two-phase, consent-sensitive submission tool with no annotations and no output schema, the description supplies the phase logic, the returned artifacts (summary, consent line, token), the human-approval gate, and the post-submission email verification. An agent could execute both calls correctly from this text alone.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3; the description adds above that by explaining that 'answers' are keyed by field key sourced from enquiry_fields, and by tying 'confirmation' to the token returned in step 1 and only to be supplied after approval. It adds sequencing semantics the flat schema cannot express, though it does not describe what an incomplete or wrongly-keyed answers object does.

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 verb and resource ('Submits an enquiry to Wärmepumpe Kosten Europa') and immediately bounds scope: 'NOT a purchase, NOT a guaranteed quote.' The title and description also point at the sibling tool enquiry_fields as the source of field keys, so an agent can tell what this tool is and is not without opening another schema.

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 two-call procedure with a gating condition ('only if the person agrees') and a required human-in-the-loop display step ('show the person the summary and the consent line'). It also states the negative cases up front (not a purchase, not a guaranteed quote). There is little left to infer about when to call this versus not.

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