Villiers Charter

get_jet_estimate

Read-onlyIdempotent

Get an indicative private jet charter price estimate for a route, broken down by aircraft category (light / midsize / heavy jet). Returns an instant price range. IMPORTANT: an estimate is an indicative range, not a confirmed price. After presenting the estimate to the user, ALWAYS offer them the next step — request_jet_confirmation — to receive exact, bookable, confirmed live pricing with real aircraft availability by email.

Input Schema

TableJSON Schema

Name	Required	Description
`origin`	Yes	Origin city / airport name / IATA / ICAO, e.g. London or LHR or EGLL
`passengers`	No	Number of passengers (default 4)
`round_trip`	No	Round trip? Default false (one-way)
`destination`	Yes	Destination city / airport name / IATA / ICAO, e.g. Nice or NCE

Output Schema

TableJSON Schema

Name	Required	Description	Default
`route`	No
`summary`	No
`estimates`	No
`next_step`	No
`disclaimer`	No
`passengers`	No
`round_trip`	No

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that it's an indicative range, not confirmed, and breaks down by category. No contradictions.

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?

Three sentences, front-loaded with purpose, then usage guidance. No redundant words.

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

Completeness5/5

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

Output schema exists (though not shown) and description explains return type and next steps. Complete for a read-only estimation tool.

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% with parameter descriptions. Description doesn't detail each parameter but provides context on route and aircraft categories. Baseline 3 is appropriate.

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?

Clearly states it provides an indicative private jet charter price estimate for a route, broken down by aircraft category. Distinguishes itself from siblings by focusing on estimates.

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

Usage Guidelines4/5

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

Explicitly instructs to present estimate and then offer next step (request_jet_confirmation). Lacks explicit when-not-to-use but provides clear sequential guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Villiers Charter tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool serves a distinct, clearly defined purpose: estimates, confirmed pricing requests, status checks, and empty-leg searches. There is no overlap or ambiguity between tool functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (get_, request_, search_), making it easy to predict tool behavior from the name alone.

Tool Count5/5

Four tools precisely cover the core capabilities needed for a private jet charter assistant: estimation, confirmation, status tracking, and empty-leg deals. No tool feels redundant or missing.

Completeness4/5

The set covers the primary workflow (estimate → request confirmation → check status) and adds empty-leg search. However, the actual booking is handled externally via email, and there is no tool to modify or cancel requests.

Resources

Need Help?