Skip to main content
Glama

get_deal

Read-onlyIdempotent

One Sparkflights fare by the numeric id from search_deals: its itinerary, the price text of its fare page, its outbound and return flights, the date pairs its fare page lists with their prices, and its url, route_url and feed_url. A fare Sparkflights no longer lists returns an error naming its route page.

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": {
      "id": "<id>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDeal ID

Output Schema

NameRequiredDescriptionDefault
dealNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "The one deal the card shows, or an error.",
      +  "properties": {
      +    "deal": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "airline": {
      +          "type": "string"
      +        },
      +        "cabin_class": {
      +          "type": "string"
      +        },
      +        "date_options": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "price_usd": {
      +                "type": "number"
      +              },
      +              "return_date": {
      +                "type": "string"
      +              },
      +              "start_date": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "start_date",
      +              "price_usd"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "destination": {
      +          "type": "string"
      +        },
      +        "destination_city": {
      +          "type": "string"
      +        },
      +        "destination_image_url": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "integer"
      +        },
      +        "origin": {
      +          "type": "string"
      +        },
      +        "origin_city": {
      +          "type": "string"
      +        },
      +        "photo_credit": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "photographer": {
      +              "type": "string"
      +            },
      +            "photographer_url": {
      +              "type": "string"
      +            },
      +            "unsplash_url": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "photographer",
      +            "photographer_url",
      +            "unsplash_url"
      +          ],
      +          "type": "object"
      +        },
      +        "price_panel": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "airline_direct": {
      +              "type": "string"
      +            },
      +            "checked_at": {
      +              "format": "date-time",
      +              "type": "string"
      +            },
      +            "cost_per_mile": {
      +              "type": "string"
      +            },
      +            "departs": {
      +              "type": "string"
      +            },
      +            "fare_brand": {
      +              "type": "string"
      +            },
      +            "local_price": {
      +              "type": "string"
      +            },
      +            "lower_cabin": {
      +              "type": "string"
      +            },
      +            "price": {
      +              "type": "string"
      +            },
      +            "returns": {
      +              "type": "string"
      +            },
      +            "seller": {
      +              "type": "string"
      +            },
      +            "seller_type": {
      +              "type": "string"
      +            },
      +            "ticketing_note": {
      +              "type": "string"
      +            },
      +            "trip": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "price",
      +            "trip"
      +          ],
      +          "type": "object"
      +        },
      +        "route_url": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        },
      +        "verified_at": {
      +          "format": "date-time",
      +          "type": "string"
      +        },
      +        "watch_url": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "url",
      +        "origin",
      +        "origin_city",
      +        "destination",
      +        "destination_city",
      +        "airline",
      +        "cabin_class",
      +        "price_panel"
      +      ],
      +      "type": "object"
      +    },
      +    "error": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "code",
      +        "message"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  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, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered structurally. The description adds one genuinely new behavioral fact: a fare Sparkflights no longer lists returns an error naming its route page, which tells the agent how a stale id fails. Beyond that it mostly enumerates return fields rather than disclosing further behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and id provenance are front-loaded in the opening clause, and the error behavior is a compact second sentence. The middle run of enumerated return fields is list-heavy and would be redundant if the output schema documents them, but overall the text is dense rather than padded.

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?

The definition covers input provenance and the failure mode for delisted fares, which is what an agent needs to call it correctly. Because an output schema exists, the long enumeration of returned fields is largely redundant rather than compensating for a gap, so completeness is adequate but not economical.

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 a single required 'id' parameter, so the baseline is 3 and the schema already carries the definition. The description adds only provenance ('numeric id from search_deals'), which is mildly useful but not a meaningful extension of the parameter's semantics.

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?

States a specific verb and resource ('One Sparkflights fare by the numeric id') and pins the id's provenance to the sibling search_deals, so an agent can tell it apart from the search tool without opening a schema. It also characterizes what the fare record contains, leaving no ambiguity about what is being fetched.

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?

The phrase 'by the numeric id from search_deals' tells the agent where to obtain the required input and thereby when this tool is appropriate versus searching. It gives no explicit exclusion or when-not guidance beyond the delisted-fare error case, so it stops short of full routing guidance.

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.