Skip to main content
Glama

BEEP.rent — car rental in Poland

Confirm a reservation with the user's code

confirm_reservation_code
Idempotent

Use when the user gives you the 6-digit code they received for a new reservation. Never guess or invent a code. Returns the reservation status: the rental company may still have to accept it. Example: {"reservation_number":"AB12CD34","status_token":"from_reservation","code":"123456"}.

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": {
      "reservation_number": "<reservation_number>",
      "status_token": "<status_token>",
      "code": "<code>"
    },
    "name": "confirm_reservation_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 6-digit code the user received.
marketNo
status_tokenYes
reservation_numberYes

Output Schema

NameRequiredDescriptionDefault
linksNo
reasonNo
statusNook
paymentNo
messagesNo
policiesNo
expires_atNo
next_stepsNo
reservationNo
capabilitiesNo
confirmationNo
continue_urlNo
has_recoveryNo
recovery_urlNo
extension_blockNo
content_languageNo
partner_decisionNo
reservation_numberNo
partner_confirmationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / extension_block
      Added value: +{
      +  "anyOf": [
      +    {
      +      "properties": {
      +        "code": {
      +          "title": "Code",
      +          "type": "string"
      +        },
      +        "user_notice": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ],
      +          "default": null,
      +          "title": "User Notice"
      +        }
      +      },
      +      "required": [
      +        "code"
      +      ],
      +      "title": "ExtensionBlockSummary",
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • changedOutput schema / properties / partner_confirmation / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "type": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "title": "Type"
      -      },
      -      "window_hours": {
      -        "anyOf": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "title": "Window Hours"
      -      }
      -    },
      -    "title": "PartnerConfirmation",
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "badge": {
      +        "anyOf": [
      +          {
      +            "properties": {
      +              "kind": {
      +                "anyOf": [
      +                  {
      +                    "type": "string"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ],
      +                "default": null,
      +                "title": "Kind"
      +              },
      +              "usual_confirmation_minutes": {
      +                "anyOf": [
      +                  {
      +                    "type": "integer"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ],
      +                "default": null,
      +                "title": "Usual Confirmation Minutes"
      +              },
      +              "window_minutes": {
      +                "anyOf": [
      +                  {
      +                    "type": "integer"
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ],
      +                "default": null,
      +                "title": "Window Minutes"
      +              }
      +            },
      +            "title": "ConfirmationBadge",
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null
      +      },
      +      "tier": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Tier"
      +      },
      +      "type": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Type"
      +      },
      +      "window_hours": {
      +        "anyOf": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Window Hours"
      +      }
      +    },
      +    "title": "PartnerConfirmation",
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false with idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context that the outcome is not final ('the rental company may still have to accept it'), but it says nothing about what happens on an invalid or expired code, which is the main failure mode for a confirmation call.

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?

Front-loaded with the trigger condition and the guardrail, then the outcome, then a compact example. The example is doing real work by illustrating parameter shape, so it earns its place, though the phrasing is slightly padded by the example's punctuation.

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

Completeness3/5

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

An output schema exists, so not describing return fields is acceptable, and the note about pending acceptance covers the result's meaning. However, for a tool with four parameters at 25% description coverage and a required status_token that is undocumented everywhere but an example, the description leaves an agent unsure how to source two of the required inputs.

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 only 25%, yet the description compensates partially with a concrete example that shows all three required parameters together and reveals that status_token takes a sentinel-like value ('from_reservation'). The required reservation_number and status_token (16-512 chars) still lack any explanation of format or provenance outside the example, and market is never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('confirm' + 'reservation code') and anchors it to a concrete trigger: the user handing over a 6-digit code. It does not explicitly contrast with the closely named sibling request_confirmation_code, so the agent must infer the request-vs-confirm split.

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?

Gives a clear when-to-use condition ('when the user gives you the 6-digit code they received for a new reservation') plus a negative guardrail ('Never guess or invent a code'). It stops short of naming an alternative for the case where the user has no code yet (presumably request_confirmation_code).

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