Skip to main content
Glama

Search charter prices

search_charter
Read-only

Prices a private jet charter for a route of 1-5 legs (a round trip is 2 legs) with Mirai Flights operators. Returns options sorted by price, each with suggestion_id and company_id for get_charter_option. Operators answer for up to 40 seconds; complete is false when more options can be fetched with get_charter_results.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "legs": "<legs>"
    },
    "name": "search_charter"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYesroute legs in order
currencyNocurrency the user asked for; default EUR, follow-ups keep the search currency
languageNoresponse language; defaults to the client's Accept-Language, then en
aircraft_class_idNoonly this class; id from list_aircraft_classes

Output Schema

NameRequiredDescriptionDefault
routeYesthe searched legs
optionsYes
task_idYes
completeYes
expires_atYesafter this time run search_charter again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / expires_at
      Added value: +{
      +  "description": "after this time run search_charter again",
      +  "type": "string"
      +}
    • addedOutput schema / properties / options / items / properties / aircraft_class
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / options / items / properties / discount_percent
      Added value: +{
      +  "type": "integer"
      +}
    • changedOutput schema / properties / options / items / properties / image / description
      Previous value: -"aircraft photo URL"New value: +"aircraft type picture URL"
    • addedOutput schema / properties / options / items / properties / price_before_discount
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "amount": {
      +      "type": "integer"
      +    },
      +    "currency": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "amount",
      +    "currency"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • addedOutput schema / properties / options / items / properties / seats
      Added value: +{
      +  "description": "seating as the site words it",
      +  "type": "string"
      +}
    • addedOutput schema / properties / route
      Added value: +{
      +  "description": "the searched legs",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "departure": {
      +        "type": "string"
      +      },
      +      "from": {
      +        "type": "string"
      +      },
      +      "from_city": {
      +        "type": "string"
      +      },
      +      "from_ref": {
      +        "type": "string"
      +      },
      +      "luggage": {
      +        "type": "integer"
      +      },
      +      "pax": {
      +        "type": "integer"
      +      },
      +      "to": {
      +        "type": "string"
      +      },
      +      "to_city": {
      +        "type": "string"
      +      },
      +      "to_ref": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "from",
      +      "to",
      +      "from_city",
      +      "to_city",
      +      "from_ref",
      +      "to_ref",
      +      "departure",
      +      "pax",
      +      "luggage"
      +    ],
      +    "type": "object"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "complete",
      -  "task_id",
      -  "options"
      -]New value: +[
      +  "complete",
      +  "task_id",
      +  "route",
      +  "expires_at",
      +  "options"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / options / items / properties / image
      Added value: +{
      +  "description": "aircraft photo URL",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: operators can take up to 40 seconds to answer, results are sorted by price, and partial results are signaled by complete=false with a follow-up fetch path. It does not cover error behavior, timeout outcomes, or rate limits.

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 the core action and constraints, followed by return/follow-up behavior and then latency/completeness. Every sentence carries useful information without repetition.

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 an open-world search tool with an output schema and annotations covering safety, the description supplies the key operational context: leg limits, sorted partial results, the 40-second latency, and how to continue fetching. It could add no-results or error handling, but is otherwise complete enough to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful domain semantics by clarifying that the legs parameter supports 1-5 legs and that a round trip counts as 2 legs. Other parameter details are left to the schema, which already documents them.

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?

The description uses a specific verb and resource: 'Prices a private jet charter for a route of 1-5 legs ... with Mirai Flights operators.' It clearly distinguishes this pricing/search operation from the sibling tools get_charter_option and get_charter_results, which it names.

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?

It gives clear follow-up routing: returned options carry suggestion_id and company_id for get_charter_option, and complete=false means more options can be fetched with get_charter_results. It does not explicitly state when to prefer alternatives like search_empty_legs or mention prerequisites such as find_location for location refs.

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.