Skip to main content
Glama

ablakarajanlat.hu Nyílászáró MCP

confirm_quote

Idempotent

A request_quote MÁSODIK lépése: az ügyfél email-címére küldött 6 jegyű megerősítő kód beváltása. A kódot a FELHASZNÁLÓTÓL kérd el (a saját postafiókjában találja) — SOHA ne találd ki és ne próbálgasd (5 hibás próba után a kérés zárolódik). Sikeres megerősítés után jut el az ajánlatkérés a munkatársakhoz. Step 2 of request_quote: redeem the 6-digit email code obtained from the user.

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": {
      "leadId": "<leadId>",
      "code": "<code>"
    },
    "name": "confirm_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesA felhasználó email-jére érkezett 6 jegyű kód (a felhasználótól kérd el).
leadIdYesA request_quote válaszában kapott leadId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the generic profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false); the description adds non-obvious behavior beyond them: a hard 5-attempt lockout that blocks the request, and the fact that the quote request is only forwarded to staff after successful confirmation. These are exactly the operational risks an agent needs before calling.

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 critical constraint (do not guess, lockout risk) is front-loaded and the English sentence is a tight condensed summary rather than a full duplication of the Hungarian. The bilingual format costs some length, but no sentence is pure filler.

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

Completeness4/5

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

For a two-parameter mutation with no output schema, the description covers prerequisites, input provenance, failure behavior, and post-success effect, which is close to everything needed to call it correctly. It stops short of saying what the immediate response contains (e.g., confirmation payload vs. error shape), a minor gap given no output schema exists.

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 coverage is 100%, so both parameters are already documented, and the description mostly reinforces the schema (code comes from the user's mailbox, leadId comes from the request_quote response). It adds the meaningful constraint that the code must be obtained from the user rather than invented, which is behaviorally useful but largely duplicative of the schema wording.

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+resource ('redeem the 6-digit email code') and explicitly positions itself as 'Step 2 of request_quote', which cleanly separates it from the sibling request_quote (step 1). The downstream effect ('after successful confirmation the request reaches staff') further pins down what the call accomplishes.

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 explicit when-to-use (second step of request_quote, after the user received the code by email), explicit source for the input (ask the user, it is in their mailbox), and an explicit prohibition with consequence (never guess or brute-force — 5 failed attempts lock the request). This is the full when/when-not pattern.

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