Skip to main content
Glama

BEEP.rent — car rental in Poland

Send the confirmation code again

request_confirmation_code

Use when the user did not receive the 6-digit code for a new reservation or it expired. Sends a new code to the contact given at booking; do not call it unprompted. Example: {"reservation_number":"AB12CD34","status_token":"from_reservation"}.

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>"
    },
    "name": "request_confirmation_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, and the description adds real value on top: the side effect is an outbound message to the booking contact, and it must not be triggered without user request. It does not say whether issuing a new code invalidates the previous one or whether repeated calls are rate-limited, which matters for a non-idempotent send.

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?

Three compact sentences: trigger, effect, restriction, plus an inline call example. The usage condition is front-loaded and nothing is redundant.

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?

Return values need not be explained because an output schema exists, and the description covers the trigger, the side effect, and the constraint against unsolicited calls. The only meaningful hole for a tool of this simplicity is the undocumented optional market parameter.

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 0%, so the description carries the burden. The example conveys the format of reservation_number ('AB12CD34') and hints at the provenance of status_token ('from_reservation'), which is genuinely useful. The 'market' parameter (enum pl-pl/en-pl) is never mentioned, leaving one of three parameters undocumented anywhere.

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 names a specific action (send the confirmation code again) and its resource context: the 6-digit code for a new reservation, delivered to the contact given at booking. It is clearly distinct from confirm_reservation_code by implication (this re-sends rather than verifies), but it never names that sibling, so differentiation is inferred rather than stated.

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?

It gives an explicit trigger ('user did not receive the 6-digit code ... or it expired') and an explicit prohibition ('do not call it unprompted'), which is stronger than most definitions. What it lacks is a naming of the alternative path (confirm_reservation_code when the user has a code in hand), so the mapping to siblings is left implicit.

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