Delta Air Lines MCP Server

login

Initiate Delta Air Lines login to access flight bookings, seat selection, check-in, and SkyMiles management through automated browser sessions.

Instructions

Initiate Delta Air Lines login flow. Opens the Delta sign-in page and saves your session. After logging in, use status to verify.

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": "login"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: 'Opens the Delta sign-in page' (implies a UI interaction) and 'saves your session' (implies state persistence). However, it lacks details on authentication requirements, error handling, or rate limits, leaving gaps for a login tool.

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?

The description is front-loaded with the main purpose, followed by additional context in two concise sentences. Every sentence adds value: the first explains the action, the second provides usage guidance. There is no wasted text.

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

Completeness3/5

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

Given the tool's complexity (login flow with session management) and no annotations or output schema, the description is somewhat complete but lacks details on return values, error cases, or prerequisites. It covers the basic flow but could benefit from more behavioral context for a secure operation.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary details.

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 clearly states the tool's purpose: 'Initiate Delta Air Lines login flow' and 'saves your session'. It specifies the action (initiate login flow) and resource (Delta Air Lines), though it doesn't explicitly differentiate from sibling tools like 'logout' or 'status' beyond mentioning the latter.

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?

The description provides clear context for usage: 'After logging in, use status to verify.' This indicates when to use this tool (to start login) and what to do next, though it doesn't explicitly state when not to use it or compare it to alternatives among siblings.

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

Deploy Server