Skip to main content
Glama

Airsockfly

Get flight fare rules

get_flight_fare_rules
Read-onlyIdempotent

Get the fare rules of a flight offer: baggage, changes and refunds. The offer is re-priced with the airline on the first call.

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": {
      "externalId": "<externalId>"
    },
    "name": "get_flight_fare_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
externalIdYesOffer identifier (externalId) returned by a search tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds genuine context beyond them: the offer is re-priced live with the airline on the first call, warning the agent of latency and possible price movement. It does not discuss failure modes or caching of subsequent calls, so it falls short of a 5.

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 tightly written sentences with zero waste; the returned content is front-loaded and the behavioral caveat follows. Every clause carries 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?

For a one-parameter read-only lookup with no output schema, the description covers what the tool returns conceptually and flags the re-pricing side effect. Only minor gaps remain, such as what happens if re-pricing fails or how the rules are structured in the response.

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% and the single externalId parameter is fully documented in the schema as an offer identifier from a search tool. The description adds no format, sourcing, or validity details beyond that, so the baseline 3 applies.

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 ('Get the fare rules of a flight offer') and enumerates the sub-content returned (baggage, changes, refunds). It is clearly distinguishable from get_offer or search_flights by naming fare rules rather than the offer itself, though it does not explicitly contrast with those siblings.

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 is only implied: the schema note that externalId comes 'from a search tool' suggests calling this after a search, and the description implies it is a follow-up to an offer lookup. There is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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