Skip to main content
Glama
Sign In
@striderlabs/mcp-american

@striderlabs/mcp-american

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_aadvantage

Check your AAdvantage miles balance, elite status, and account summary. Requires being logged in to American Airlines.

Instructions

Check AAdvantage miles balance, elite status, and account summary. Requires being logged in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

There are no annotations, so the description must convey behavior. It states a key precondition (authentication) and implies a read-only operation via 'Check.' However, it does not disclose output format, error behavior, or any side effects, which are relevant for an unannotated 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?

Two short sentences that are front-loaded with the action and resource. No waste.

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 simple read-only tool with no parameters, the description covers the purpose and a precondition. It lacks explicit return-value details, but the summary of what is checked (balance, status, summary) sufficiently conveys the expected output for a basic check.

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?

The input schema has zero parameters, so there is nothing to clarify. The description appropriately omits parameter details.

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 uses the specific verb 'Check' and clearly identifies the resource: AAdvantage miles balance, elite status, and account summary. This distinguishes it from sibling tools like get_reservation or status by specifying the exact domain (AAdvantage account).

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?

The only guidance is 'Requires being logged in,' which is a prerequisite rather than a when-to-use instruction. It does not explicitly compare with alternatives like status or get_reservation, so the agent must infer from the domain.

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

Deploy Server

Other Tools