Skip to main content
Glama

PRIVYDE Private Chauffeur

List the cities Privyde serves

list_cities
Read-onlyIdempotent

List the cities Privyde serves. Madrid is the base (local transfers, airport, chauffeur at disposal); the others are ends of long-distance trips in both directions, with no local service inside them.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious domain behavior: coverage is asymmetric, with local services only in Madrid and the other cities served solely as trip endpoints, which materially affects how an agent should interpret and act on the result. It stops short of describing result shape or ordering.

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?

Two sentences with no filler. The core purpose leads, and the service-model caveat follows immediately, so the most decision-relevant fact (Madrid-only local service) is front-loaded rather than buried.

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-parameter, read-only listing tool with no output schema, the description covers what the list contains and the semantic asymmetry between cities. The only gap is that it never characterizes the response (city names plus URLs, per the lang parameter's wording), which the absence of an output schema would otherwise make worth stating.

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 100% schema description coverage, including its enum and default of "es", so the schema does the heavy lifting. The description adds nothing about localization — notably that lang affects returned names and URLs, a detail visible only in the schema.

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 ("List the cities Privyde serves") and immediately qualifies the domain: Madrid is the home base with local transfers, while the other cities are only endpoints of long-distance trips. That distinction separates it from route- or fleet-oriented siblings like list_popular_routes and list_fleet without needing to open a schema.

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 only implied — an agent can infer this is the catalog call to make when it needs to know which cities are serviceable. There is no explicit when-to-use/when-not-to-use statement and no naming of an alternative for related questions such as pricing (get_quote) or route availability (list_popular_routes).

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