Skip to main content
Glama

Get one empty leg

get_empty_leg
Read-onlyIdempotent

Current details of one offer by the ref returned by search_empty_legs. available=false means the offer is no longer listed.

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": {
      "ref": "<ref>"
    },
    "name": "get_empty_leg"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesref exactly as returned by search_empty_legs.
localeNoLanguage of texts and links in the result: en or de.en

Output Schema

NameRequiredDescriptionDefault
notesNo
flightYes
data_as_ofYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale / description
      Added value: +"Language of texts and links in the result: en or de."
  2. Changed2 schema fields changed
    • changedOutput schema / $defs / AgentFlight / properties / inquiry_possible / description
      Previous value: -"False for partner offers, which are requested on the partner site via the url."New value: +"False for offers listed by a partner, which are requested on the partner site via the url."
    • changedOutput schema / $defs / AgentFlight / properties / inquiry_url / description
      Previous value: -"Offer page with the inquiry form opened and pre-filled. The user enters name and email and sends it. Null for partner offers."New value: +"Offer page with the inquiry form opened and pre-filled. The user enters name and email and sends it. Null for offers listed by a partner."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds genuinely useful behavior beyond them: 'available=false means the offer is no longer listed' tells the agent how to interpret a stale-looking result. It does not mention rate limits or how quickly offers go stale, and the return shape is covered by the output schema.

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 purpose and followed by the result-interpretation rule. No filler, no repetition of the title or parameter names.

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 two-parameter read tool with full schema coverage and an output schema, the description covers what it returns, where the key comes from, and how to read the availability flag. Only minor gaps remain, such as how fresh the details are or whether repeated calls should be polled.

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%, including an explicit description on the ref parameter and an enum for locale, so the schema does the heavy lifting. The description reinforces where ref comes from but says nothing about locale, so it adds only marginal meaning beyond the structured fields — 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?

The description names a specific resource ('Current details of one offer') and ties it to the singular lookup as opposed to the sibling search_empty_legs, so an agent can distinguish it from the search tool. The only weakness is that the retrieval verb is implied by 'details of' rather than stated outright, but the intent is unambiguous.

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?

'by the ref returned by search_empty_legs' gives clear routing context: this is the follow-up call after a search. It does not state a when-not condition (e.g., re-search instead of polling this repeatedly for changed results), so it falls short of full exclusion 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