Skip to main content
Glama

PRIVYDE Private Chauffeur

Get Privyde company info: what it offers, coverage, fleet, contact channels (WhatsApp 24/7 and email), how booking and payment work, prices from, minimum notice and cancellation, all read live from the rate card

get_company_info
Read-onlyIdempotent

Get Privyde company info: what it offers, coverage, fleet, contact channels (WhatsApp 24/7 and email), how booking and payment work, prices from, minimum notice and cancellation, all read live from the rate card.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare safe read-only, idempotent, closed-world behavior, so the bar is lower. The description adds genuinely new context ('read live from the rate card'), signaling that prices and terms reflect real-time rate-card data rather than static copy — useful for trusting the values. It does not discuss caching, rate limits, or output shape beyond the enumerated topics.

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?

A single front-loaded sentence that leads with the resource and then lists coverage areas in a scannable series. Dense but every clause carries information; the parenthetical about WhatsApp 24/7 and email is slightly verbose but legitimately 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?

With no output schema, the description carries the return-value burden and does so by enumerating the content categories an agent will receive. Combined with annotations covering the safety profile, the only material gap is the absence of any mention of the lang parameter's effect on returned names and URLs.

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 parameter has an enum with default documented in the schema. The description mentions nothing about localization or the lang parameter, so it adds no meaning beyond what the schema already supplies; 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+resource (company info) and enumerates the concrete content returned: offers, coverage, fleet, contact channels, booking/payment mechanics, prices from, minimum notice and cancellation. It doesn't explicitly differentiate itself from overlapping siblings like list_fleet or list_cities, which return subsets of this data, leaving an agent to infer the boundary.

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 orientation/overview call an agent should make before digging into list_cities, list_fleet, or get_quote, but no sentence says when to prefer those tools or in what order. No exclusion or prerequisite is stated.

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