Skip to main content
Glama

BEEP.rent — car rental in Poland

List my reservations

list_my_reservations
Read-onlyIdempotent

Use when the user asks about their own BEEP.rent bookings. Lists the reservations of the e-mail the user verified with start_reservation_management (pass its management_id) or of the BEEP.rent account they connected: upcoming ones with the next pickup first, or with include_past the last 365 days, newest first. Each has its number, status, dates, pickup place, car and total. Example: {"management_id": "from_verify", "limit": 5}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_reservations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many reservations to return.
offsetNo
include_pastNoAlso list rentals that ended or were cancelled in the last 365 days.
management_idNoFrom verify_reservation_management for the user's e-mail.

Output Schema

NameRequiredDescriptionDefault
linksNo
statusNook
messagesNo
policiesNo
expires_atNo
next_stepsNo
paginationNo
continue_urlNo
reservationsNo
content_languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds genuine context: sort order (next pickup first, or newest first with include_past), the 365-day lookback, and the returned fields. Pagination behavior and the 20-item cap are not disclosed.

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?

Opens with the trigger condition, then the identity source, then ordering, then returned fields, then an example — strictly front-loaded with no filler sentences. Each sentence carries distinct 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?

With an output schema present, return values needn't be restated, yet the description still summarizes them helpfully; identity, ordering, and past-window semantics are all covered. The one gap is pagination/offset behavior for a tool whose limit can be lower than the result set is not addressed.

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?

Goes beyond the 75% coverage schema by explaining the semantics of include_past (last 365 days, reversed ordering) and where management_id comes from, plus a concrete call example. However, offset is never explained and the description credits start_reservation_management for the id while the schema says verify_reservation_management, a small source ambiguity.

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 (lists) and resource (reservations) scoped precisely to the user's own BEEP.rent bookings, which distinguishes it from siblings like search_offers or get_reservation_status. The added detail about whose bookings (verified e-mail vs connected account) removes ambiguity about scope.

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?

"Use when the user asks about their own BEEP.rent bookings" gives a clear triggering condition and the prerequisite identity flow (verify via start_reservation_management). It does not name alternatives such as get_reservation_status for a single booking or cancel_reservation, so routing against siblings is left partly to inference.

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