Skip to main content
Glama

The Bonus Stack

New, raised and ending bank bonuses

whats_changed
Read-onlyIdempotent

List bank bonuses that were added, raised, extended or ended recently, and bonuses ending soon. Use it for 'any new bank bonuses this week', 'what changed since I last checked' or 'which bonuses end this month'. Covers the last 90 days.

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_changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNoWhich changes to list. ending_soon lists bonuses whose deadline falls in the next 45 days. Defaults to all.
sinceNoThe first day to list, YYYY-MM-DD. Defaults to 7 days ago; no earlier than 90 days ago.
stateNoThe person's state, to list only bonuses open there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed-world read. The description adds real behavioral context beyond that: the 90-day lookback horizon and the precise meaning of 'changed' (added, raised, extended, ended) plus ending-soon bonuses. It does not describe result ordering or volume, but the essential behavioral frame is present.

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?

Three sentences, front-loaded with the verb and resource, then usage examples, then the time horizon. Tight and purposeful, though the change-type list at the start partially duplicates the kinds enum and the later mention of ending soon.

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 three-optional-parameter read tool with no output schema and full annotation coverage, this is nearly complete: it names the change types, the time window, and the query patterns it serves. Missing only sibling routing and any note on result ordering or limits, which keeps it from a 5.

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%, so kinds, since, and state are already fully documented including the 90-day floor and the 45-day ending_soon window. The description's 'Covers the last 90 days' and its enumeration of change types merely echo what the schema already states, adding little new meaning.

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?

States a specific verb ('List') and resource ('bank bonuses') narrowed to a change set (added, raised, extended, ended, ending soon). This distinguishes it conceptually from a general bonus search like find_bonuses, but the description never names or contrasts with that sibling, so an agent must infer the difference.

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?

Gives concrete example queries ('any new bank bonuses this week', 'what changed since I last checked', 'which bonuses end this month') that clearly anchor when to use it. It stops short of saying when not to use it or which sibling to pick for a full catalog or single-bonus lookup.

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