I Know The Pilot

Get Deal Details

get_deal

Read-only

Get full details for a specific flight deal including routes and airlines.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`deal_id`	Yes	The deal ID

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	URL to view and book the deal
`title`	No	Deal headline
`routes`	No	Flight routes available for this deal
`deal_id`	No	Unique deal identifier
`summary`	No	Brief description of the deal
`airlines`	No	Airline codes operating this deal
`currency`	No	Currency code (always AUD)
`from_price`	No	Starting price in AUD
`expiry_date`	No	Deal expiry date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "airlines": {
+      "description": "Airline codes operating this deal",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "currency": {
+      "description": "Currency code (always AUD)",
+      "type": "string"
+    },
+    "deal_id": {
+      "description": "Unique deal identifier",
+      "type": "integer"
+    },
+    "expiry_date": {
+      "description": "Deal expiry date (YYYY-MM-DD)",
+      "type": "string"
+    },
+    "from_price": {
+      "description": "Starting price in AUD",
+      "type": "integer"
+    },
+    "routes": {
+      "description": "Flight routes available for this deal",
+      "items": {
+        "properties": {
+          "destination": {
+            "description": "Destination airport code",
+            "type": "string"
+          },
+          "origin": {
+            "description": "Origin airport code",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "description": "Brief description of the deal",
+      "type": "string"
+    },
+    "title": {
+      "description": "Deal headline",
+      "type": "string"
+    },
+    "url": {
+      "description": "URL to view and book the deal",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which covers the safety profile. However, the description adds no behavioral context beyond that: no mention of auth requirements, rate limits, or any constraints. It only states the output content (routes and airlines), which is return-value information rather than behavioral disclosure.

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?

The description is a single, front-loaded sentence that conveys the purpose and key output details without redundancy. Every word earns its place, making it concise and well-structured.

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?

Given the tool's low complexity (one parameter), good schema coverage, an output schema, and read-only annotations, the description is largely complete. It could have explicitly mentioned the deal_id requirement, but the schema covers that, so the overall context is adequate.

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?

The input schema fully documents the single deal_id parameter with 100% coverage. The description does not add information about the parameter, but the schema is sufficient. A baseline of 3 is appropriate because the description contributes no extra semantic value.

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 uses a specific verb ('Get') and identifies the resource ('specific flight deal') with useful detail ('full details including routes and airlines'). It is clear and distinct enough from sibling tools like list_top_deals_from and search_deals, though it does not explicitly mention retrieval by deal ID.

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?

The phrase 'specific flight deal' implies this tool is for retrieving one deal rather than listing or searching, but the description provides no explicit guidance on when to choose this tool over siblings. The intended usage is only implied, not spelled out.

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

All I Know The Pilot 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.

Resources

Need Help?