Skip to main content
Glama

PRIVYDE Private Chauffeur

List popular point-to-point routes with indicative starting price (EUR), distance and duration

list_popular_routes
Read-onlyIdempotent

List popular point-to-point routes with indicative starting price (EUR), distance and duration.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description does add real context beyond them: prices are indicative starting prices denominated in EUR, and each route carries distance and duration. It says nothing about result volume, ordering, or whether prices include taxes.

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 dense sentence with the resource and the returned fields front-loaded; nothing is padded. It is however essentially a verbatim repeat of the title, so it carries no extra information beyond compression.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read-only list tool with a fully documented schema and clear annotations, the essentials are covered. Gaps remain around result size/ordering and what 'indicative starting price' implies (currency conversion, seasonal variation), which matter when an agent quotes these numbers to a user.

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?

Schema coverage is 100% and the single 'lang' enum parameter is fully documented in the schema, including the 'es' default. The description adds no meaning about language selection or how returned names/URLs are localized, so this sits at the baseline.

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 uses a specific verb-plus-resource ('List popular point-to-point routes') and names the payload fields (starting price in EUR, distance, duration). It is unambiguous on its own, though it never states how it differs from sibling list_* tools or from get_quote.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives such as get_quote for actual pricing. A reader must infer from the word 'popular' and 'indicative' that this is browse/inspiration rather than booking.

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