Skip to main content
Glama

Get charter option

get_charter_option
Read-only

Returns details and the booking link for one option from search_charter. Booking happens on mirai.flights or in the Mirai app.

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": {
      "task_id": "<task_id>",
      "suggestion_id": "<suggestion_id>",
      "company_id": "<company_id>"
    },
    "name": "get_charter_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYestask_id from search_charter
currencyNocurrency the user asked for; default EUR, follow-ups keep the search currency
languageNoresponse language; defaults to the client's Accept-Language, then en
company_idYes
suggestion_idYes

Output Schema

NameRequiredDescriptionDefault
legsYes
linkNobooking link for the user
imageNoaircraft type picture URL
priceYes
routeNothe searched legs
seatsNoseating as the site words it
photosNo
task_idYessearch this option belongs to
capacityNo
featuresNo
company_idYes
aircraft_typeYes
suggestion_idYes
aircraft_classNo
discount_percentNo
aircraft_class_idNo
price_before_discountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +  ]
      +}
  2. Changed7 schema fields changed
    • addedOutput schema / properties / aircraft_class
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / discount_percent
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / features / items / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / features / items / required
      Previous value: -[
      -  "name",
      -  "value"
      -]New value: +[
      +  "key",
      +  "name",
      +  "value"
      +]
    • changedOutput schema / properties / image / description
      Previous value: -"aircraft photo URL"New value: +"aircraft type picture URL"
    • addedOutput schema / properties / price_before_discount
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "amount": {
      +      "type": "integer"
      +    },
      +    "currency": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "amount",
      +    "currency"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • addedOutput schema / properties / seats
      Added value: +{
      +  "description": "seating as the site words it",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • addedOutput schema / properties / image
      Added value: +{
      +  "description": "aircraft photo URL",
      +  "type": "string"
      +}
    • addedOutput schema / properties / task_id
      Added value: +{
      +  "description": "search this option belongs to",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "suggestion_id",
      -  "company_id",
      -  "aircraft_type",
      -  "price",
      -  "legs"
      -]New value: +[
      +  "suggestion_id",
      +  "company_id",
      +  "aircraft_type",
      +  "price",
      +  "legs",
      +  "task_id"
      +]
  4. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by making clear that booking happens externally on mirai.flights or in the Mirai app, so this call only surfaces a link and performs no transaction. What it omits is whether the option can expire or how long the returned link stays valid.

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 short sentences with zero filler; the core behavior is front-loaded and the external-booking constraint follows immediately. Nothing repeats the title or the annotations verbatim.

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?

An output schema exists, so the return shape need not be described, and the external-booking fact is stated. However, for a five-parameter tool with two undocumented required IDs and no explicit guidance on sequencing relative to search_charter or get_charter_results, the definition is only minimally sufficient.

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

Parameters2/5

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

The description mentions no parameters at all, while schema coverage sits at 60%: task_id, currency and language carry descriptions, but the required company_id and suggestion_id are bare strings in the schema and unexplained in the description. The description therefore adds no meaning beyond the schema and leaves two required identifiers undocumented for a tool whose inputs are not self-evident.

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?

States a specific verb and resource: returns details plus the booking link for one option produced by search_charter. The phrase 'one option' implicitly separates it from the list-style sibling get_charter_results, though it never names that sibling or states the contrast explicitly.

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 context is only implied through the reference to search_charter as the source of task_id, so an agent can infer this is a follow-up drill-down step. There is no explicit when-not guidance, no statement about preconditions (e.g., needing a completed search), and no named alternative for fetching the full results list.

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.