Skip to main content
Glama

whats_expiring

Lists expiring card balances and unused statement credits, soonest first, showing the enrollment, booking channel, and spend requirements needed to prevent losing them.

Instructions

What the user is about to lose: balances (airline codes, earned credits, certificates) nearing expiry, and this period's card credits not yet used, soonest first, with what each needs (enrollment, booking channel, spend). Call it when planning trips or purchases, or when asked what's expiring.

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

Input Schema

NameRequiredDescriptionDefault
todayNoISO date to evaluate from; defaults to today.
within_daysNoLook-ahead window in days. Default 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses result ordering (soonest first) and that each entry reports the prerequisite action (enrollment, booking channel, spend). It leaves undiscussed whether already-expired items are included, result-size limits, or account/auth prerequisites, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The value proposition is front-loaded ('What the user is about to lose'), and the second sentence handles the call condition. The parenthetical prerequisite list is dense but each element is informative rather than filler.

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-optional-parameter read tool with no output schema, the description explains the returned content and ordering well enough to call it correctly. Minor gaps remain around the expired-vs-expiring boundary and result volume.

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% and both parameters (today, within_days) are fully documented with defaults and bounds, so the schema does the heavy lifting. The description adds no format or interpretation detail beyond that, making the baseline 3 appropriate.

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 names the exact resource set (expiring balances: airline codes, earned credits, certificates; plus this period's unused card credits) and the ordering (soonest first). An agent can tell this apart from set_balance, mark_credit, and list_cards without opening any schema.

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?

It gives concrete triggers: 'when planning trips or purchases, or when asked what's expiring.' That is clear usage context, but no explicit exclusions or named alternatives (e.g., use list_cards for card inventory) are offered.

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