Skip to main content
Glama

Airsockfly

Get offer details

get_offer
Read-onlyIdempotent

Refresh one offer by its externalId before booking. Returns the current price, availability, cancellation policy and details, or not_found when the offer has expired.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds beyond that: "Refresh" signals a live re-fetch rather than a cache read, and "not_found when the offer has expired" discloses the failure mode — genuinely useful for an agent deciding whether to trust a stale offer.

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 sentences, zero filler: the action leads, the return contract follows. Both timing context and the expiry failure mode are packed in without redundancy.

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?

With no output schema, the description must carry the return contract, and it does — listing price, availability, cancellation policy, details and the not_found case. For a two-parameter read tool with full annotation coverage, nothing an agent needs before calling is missing.

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 description coverage is 100%, so both parameters are already documented, which sets the baseline at 3. The description reinforces that externalId is the offer identifier from a search call but adds nothing about the vertical enum or identifier format beyond the schema.

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?

"Refresh one offer by its externalId" gives a specific verb and resource with single-item scope, and the return sentence enumerates what comes back (price, availability, cancellation policy, details). It also implicitly separates itself from the search_* siblings by noting the externalId originates from a search tool.

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?

"Before booking" places the call in the workflow, and "externalId returned by a search tool" tells the agent it must search first. It stops short of naming an alternative or stating when not to call it (e.g., reusing a still-valid offer), so it is clear context rather than 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.

Resources