Skip to main content
Glama

Ablakunio Nyílászáró MCP

confirm_quote

Idempotent

A request_quote után az ügyfél e-mailben kapott 6 jegyű megerősítő kód beváltása. CSAK a sikeres megerősítés után továbbítódik az ajánlatkérés az irodához. Paraméterek: a request_quote válaszában kapott lead_ref + az ügyfél által bemondott kód. A kód 30 percig érvényes, max 5 próbálkozás.

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

Input Schema

NameRequiredDescriptionDefault
codeYesAz ügyfél e-mailjére érkezett 6 jegyű kód.
lead_refYesA request_quote válaszában kapott hivatkozás.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the business consequence (the quote request is forwarded to the office only after successful confirmation) and operational limits (30-minute code validity, max 5 attempts). These are exactly the side-effect and rate-limit facts an agent cannot infer from readOnlyHint=false / destructiveHint=false.

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?

Front-loads the action and the prerequisite, then the consequence, then parameters and limits, in four dense sentences with no filler. Every clause carries actionable information.

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 state-changing tool with annotations but no output schema, the description covers prerequisites, timing, and retry limits. It stops short of saying what happens when the 5 attempts are exhausted or what a failed redemption returns, which would complete the picture.

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 coverage is 100%, so both parameters are already documented, and the description largely restates them (lead_ref from the request_quote response, code from the customer's email). The extra constraint that the code is 6 digits adds only marginal meaning beyond 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?

States a specific verb+resource: redeeming the 6-digit confirmation code the customer received after request_quote. It explicitly anchors the tool to a sibling (request_quote) so the agent can place it in the workflow without inspecting other schemas.

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?

Clear sequencing context: it is used only after request_quote, with the lead_ref taken from that response plus the code spoken by the customer. It does not name when to avoid it or what to do if confirmation fails repeatedly, but the usage context is unambiguous.

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