Skip to main content
Glama

Get more charter results

get_charter_results
Read-only

Returns the options collected so far for an unfinished search_charter call, by its task_id.

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>"
    },
    "name": "get_charter_results"
  }
}

Input Schema

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

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false. The description adds real value by disclosing that results are partial ('collected so far') and tied to an unfinished task, which explains the non-idempotent hint. It says nothing about task expiry, behavior for a completed or invalid task_id, or whether repeated calls return growing result sets.

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?

A single sentence with no filler, front-loading the return value and then the keying parameter. Nothing here could be cut without losing information.

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?

The tool is simple, has an output schema (so return shape needn't be described) and annotations covering safety, so the one-sentence description plus the task-anchoring detail is nearly sufficient. The remaining gap is task lifecycle guidance — what happens on a finished or expired task_id — which matters for a polling-style 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 67%: currency and language are fully documented in the schema, including follow-up semantics and defaults. The description partially compensates for the undocumented task_id by tying it to a search_charter call, but adds no format or lifecycle detail beyond that; baseline 3 fits.

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 ('Returns') and resource ('the options collected so far'), and anchors the tool to a named sibling by saying it operates on an unfinished 'search_charter' call. That lets an agent distinguish it from search_charter itself and from get_charter_option, though it never clarifies the get-vs-get_charter_option boundary directly.

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?

Gives a clear triggering condition: use this when a search_charter call is still unfinished and you have its task_id. It does not state explicitly when to stop calling, how often to poll, or what to do once the search completes, but the core when-to-use context is present.

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.