Skip to main content
Glama

PRIVYDE Private Chauffeur

List Privyde private chauffeur services (weddings, corporate events, airport transfers, chauffeur by the hour, etc

list_services
Read-onlyIdempotent

List Privyde private chauffeur services (weddings, corporate events, airport transfers, chauffeur by the hour, etc.).

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond that: no note on whether all services are returned or whether ordering/multi-language fallback occurs. It is essentially a restatement of the title.

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?

One sentence, front-loaded with the verb and resource, with zero filler and no trailing caveats. It is efficient, though the parenthetical is largely illustrative rather than informative.

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 simple read-only list tool with one optional parameter, rich annotations, and no output schema, the definition covers what the tool returns at a category level. The main missing piece is any description of the shape of returned items (names, URLs, IDs), which the agent would otherwise need to discover at call time.

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 only one optional parameter (lang) with an enum and 100% schema description coverage, so the schema already tells the agent it controls language for names and URLs with a default of "es". The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb (List) and resource (Privyde private chauffeur services), and the parenthetical enumerates concrete service categories, which separates it from siblings like list_cities, list_fleet, and list_popular_routes. It does not explicitly say what it is not, and it largely repeats the title verbatim.

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

Usage Guidelines2/5

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

The service examples hint at when the tool is relevant (weddings, corporate events, airport transfers, hourly chauffeur), but there is no explicit guidance on when to call this versus list_popular_routes, get_quote, or get_booking_link. An agent must infer routing from sibling names alone.

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