Skip to main content
Glama
markswendsen-code

@striderlabs/mcp-alaska

alaska_cancel_booking

Cancel an Alaska Airlines booking using a confirmation code. Verify cancellation policy first as fees may apply.

Instructions

Cancel an Alaska Airlines booking. Check cancellation policy before cancelling as fees may apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmation_codeYes6-character Alaska Airlines confirmation code
Behavior2/5

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

No annotations provided, so description must disclose behaviors. It mentions fees but does not cover authentication, side effects (e.g., refund, seat release), or whether cancellation is reversible. For a destructive action, more detail is needed.

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 concise sentences. First states purpose, second adds a crucial precaution. No wasted words.

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?

With one parameter and no output schema, the description covers the essential action and a warning. Missing details on return value or post-cancel steps, but sufficient for a simple cancellation tool.

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 clear description of confirmation_code. The top-level description adds no extra param info, so baseline score of 3 is correct.

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 clearly states the tool cancels an Alaska Airlines booking, with a specific verb and resource. It distinguishes well from sibling tools like check_in or get_booking.

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?

Explicitly advises to check the cancellation policy before proceeding, hinting at fees. No explicit when-not-to-use or alternatives, but the warning is useful for correct usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/markswendsen-code/mcp-alaska'

If you have feedback or need assistance with the MCP directory API, please join our Discord server