Skip to main content
Glama

BEEP.rent — car rental in Poland

Search long-term rental offers

search_long_term_offers
Read-onlyIdempotent

Use for a car rented for months or years (1 month renewed monthly to 3 years): monthly prices in PLN per mileage package, excluding VAT for businesses or including VAT for private customers, with the inquiry link of each package. Not for trips with dates: use search_offers. Filters take facets values; facets list them. Examples: {"rent_length":"year2","customer_type":"individual"}; {"brand":"Audi","monthly_cost_max":5000}.

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": "search_long_term_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoA value or label from facets.body.
fuelNoA value or label from facets.fuel.
brandNoA brand from facets.brand, e.g. Audi.
limitNo
marketNo
offsetNo
orderingNo
rent_lengthNoflex = 1 month, renewed monthly; month3, month6; year1, year2, year3.year1
transmissionNo
customer_typeNobusiness: prices excluding VAT; individual: including VAT.business
monthly_cost_maxNoPLN per month, in the customer_type's unit (gross for individual).
monthly_cost_minNoPLN per month, in the customer_type's unit (gross for individual).
production_year_maxNo
production_year_minNo

Output Schema

NameRequiredDescriptionDefault
linksNo
facetsNo
offersNo
statusNook
messagesNo
page_urlNo
policiesNo
expires_atNo
next_stepsNo
paginationNo
price_basisNo
rent_lengthNo
continue_urlNo
customer_typeNo
content_languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / body / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 64,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 64,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / brand / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 64,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 64,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / fuel / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 64,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 64,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so credit goes to what the description adds: currency (PLN), that prices are per mileage package and net-of-VAT for business vs gross for individual, and that each package carries an inquiry link. It does not mention pagination behaviour, which matters because limit/offset exist.

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 use case, then the exclusion, then the facet-value rule, then two compact examples — everything is front-loaded and each clause carries information. The example JSON payloads remove ambiguity at very low token cost.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description covers the domain-specific traps (VAT unit, rent_length meaning, facet-sourced values). The one residual hole is that it never says where to obtain the facet listings it tells the agent to use, and pagination is unaddressed.

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?

Schema coverage is only 50%, but the description compensates with the key addition that filter values come from facets, plus concrete examples showing rent_length, customer_type, brand and monthly_cost_max in use — and it restates the VAT unit dependency that governs the cost filters. It leaves several parameters (market, ordering, transmission, production_year_min/max, limit/offset) entirely to the schema, so not quite full compensation.

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 and resource plus scope: cars rented 'for months or years (1 month renewed monthly to 3 years)', with the returned price semantics (monthly PLN per mileage package) and VAT treatment. It also names the sibling it is not — 'Not for trips with dates: use search_offers' — so an agent can route without opening either schema.

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?

Explicit when-to-use (long-term rental) and when-not (dated trips -> search_offers), plus a non-obvious invocation rule: 'Filters take facets values; facets list them', backed by two worked example filter payloads. This is the level of routing guidance that prevents a mis-selection against search_offers.

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