Skip to main content
Glama

BEEP.rent — car rental in Poland

Request a rental extension

request_extension
DestructiveIdempotent

Use after quote_extension when the user asked to extend. First call without confirm previews the request and returns confirmation_token; after the user's explicit yes call again with confirm=true, the token and the same new_return_at. Show user_notice verbatim when present and add nothing. The rental company decides; decision says how the user hears back. Example: {"management_id":"from_verify","new_return_at":"2026-12-10T10:00:00+01:00","confirm":true,"confirmation_token":"from_preview"}.

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": {
      "new_return_at": "<new_return_at>"
    },
    "name": "request_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNo
confirmNofalse previews; true executes the previewed operation.
management_idNoFrom verify_reservation_management.
new_return_atYes
confirmation_tokenNo
reservation_numberNoThe number of one of the user's own reservations.

Output Schema

NameRequiredDescriptionDefault
linksNo
quoteNo
reasonNo
statusNook
decisionNo
messagesNo
policiesNo
replayedNo
expires_atNo
extendableNo
next_stepsNo
request_idNo
user_noticeNo
continue_urlNo
content_languageNo
confirmation_tokenNo
reservation_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / user_notice
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "User Notice"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is partly covered. The description adds valuable behavior: preview returns a confirmation_token, execution requires explicit confirmation, user_notice must be shown verbatim, and the rental company makes the decision. It does not spell out the destructive consequences of confirming, but it does not contradict the annotations either.

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 description is front-loaded with the usage condition and then gives the two-step procedure, user_notice handling, and outcome. The example is compact and useful for field mapping, though the sentence structure is dense. Every element roughly earns its place.

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 destructive, open-world mutation with an output schema, the definition covers the essential interaction pattern: preview, explicit confirmation, token reuse, and user_notice display. The output schema can carry return-value details, and annotations carry idempotency and destructive hints. A brief note on the consequence of confirming would make it fully complete, but it is adequate.

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?

With 50% schema description coverage, the description compensates for the critical confirmation flow by explaining that confirm=false previews, confirm=true executes, the confirmation_token comes from the preview, and new_return_at must be reused. The example also clarifies management_id and token provenance. It leaves market and res_number less explained, but the core risky parameters are covered well beyond bare schema text.

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?

The description states a specific action and resource: requesting a rental extension after quote_extension. It clearly distinguishes itself from the quoting step and explains the preview/confirm flow, so an agent can tell what this tool is for without ambiguity.

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?

It explicitly says to use this after quote_extension when the user asked to extend, and it gives the exact call sequence: preview first without confirm, then execute only after the user's explicit yes with confirm=true and the same token and new_return_at. This is strong operational guidance with a clear alternative named.

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