Skip to main content
Glama

Get latest flight deals

get_latest_deals
Read-only

Fetch the latest cheap flight deals from the Friday Flight Deals newsletter (title, url, date, summary) to answer a question about them. It shows a deals widget, so skip it if open_friday_flight_deals was already called.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_latest_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful behavioral context beyond annotations by noting that calling it shows a deals widget and by warning against a duplicate call after open_friday_flight_deals.

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, front-loaded with the fetch action and followed by the skip condition. Every clause adds useful information: purpose, returned fields, widget behavior, and duplicate-call avoidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description is complete enough: it names the source, lists the four returned fields, explains the widget behavior, and gives the duplicate-call exclusion. No critical calling information is missing.

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?

The tool takes no parameters, so there are no parameter semantics to clarify; this meets the baseline of 4. The description instead lists return fields, which is helpful but does not change the parameter score.

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 ('Fetch') and resource ('latest cheap flight deals from the Friday Flight Deals newsletter'), and explicitly lists the returned fields (title, url, date, summary). It also distinguishes this tool from the sibling open_friday_flight_deals by stating the skip condition.

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 a clear usage context ('to answer a question about them') and an explicit when-not condition: skip if open_friday_flight_deals was already called. It does not mention other sibling alternatives such as find_route_fares or check_hidden_city_ticket, so it falls short of fully explicit alternative routing.

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.

Resources