Skip to main content
Glama

PRIVYDE Private Chauffeur

List Privyde vehicles with capacity (passengers, luggage) and category

list_fleet
Read-onlyIdempotent

List Privyde vehicles with capacity (passengers, luggage) and category. The Mercedes-Benz V300 Atelier Collection is the main vehicle (own fleet, bookable on the website); the other categories are on request, subject to confirmation.

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_fleet"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for names and URLs. Defaults to "es".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile is covered. The description adds genuine domain context beyond that — the V300 Atelier Collection is own-fleet and website-bookable while other categories are subject to confirmation — but it says nothing about the shape of the returned list or whether the enumeration is exhaustive.

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?

Two sentences, front-loaded with the resource and the attributes returned, with no filler. The second sentence is denser than ideal but every clause carries information an agent would otherwise have to guess.

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 one-optional-parameter read-only list tool with no output schema and full annotation coverage, the definition supplies the key commercial nuance an agent needs to avoid over-promising availability. The main residual gap is the absence of any indication of what a fleet entry looks like, though the title partially fills that.

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?

There is a single optional 'lang' parameter with full schema coverage, an enum of six languages, and a stated default of 'es'. The description adds no meaning beyond that and does not state that language affects vehicle names and URLs, so it neither compensates nor detracts; baseline 3 applies.

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 verb and resource ('List Privyde vehicles') and specifies the attributes surfaced (capacity for passengers and luggage, category), which distinguishes it from sibling list tools covering cities, routes, or services. It does not explicitly contrast itself with those siblings, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for browsing fleet options, and the second sentence gives useful selection context (which vehicle is directly bookable vs. on request). There is no explicit when-to-use or when-not-to-use framing against alternatives such as get_quote or get_booking_link.

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