Skip to main content
Glama

The Bonus Stack

Find bank bonuses

find_bonuses
Read-onlyIdempotent

Find current US bank account bonuses a person can get: cash a bank pays for opening a checking, savings or fintech account and meeting its requirements. Use this for questions like 'what bank bonuses can I get in Ohio', 'bonuses that need no direct deposit', 'best checking bonus with no monthly fee' or 'savings bonuses ending soon'. Always pass the person's state when you know it, because many offers are limited to certain states. Returns up to 10 offers in The Bonus Stack's own order, each with the amount, the main requirement, the deadline, the date we last verified it, a link to its page and an apply link. For the full terms of one offer, call get_bonus.

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

Input Schema

NameRequiredDescriptionDefault
sortNobest is easiest first, then the larger amount. ending_soon puts the nearest deadline first.best
limitNoHow many offers to return, 1 to 10.
stateNoTwo-letter US state code, such as OH or TX.
searchNoBank, account or requirement words, matched the way the search box on thebonusstack.com/bonuses matches them.
filtersNoNarrow the list. Every filter named must hold.
account_typeNoAccount type. portal lists cashback portal routes, which the other types leave out. With direct_deposit not_required the list is the no-direct-deposit page's own, which includes the portal options it shows.any
direct_depositNonot_required lists only bonuses a person can earn without a direct deposit.any

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint true, destructiveHint false, idempotent, closed-world), and the description adds behavior beyond them: a cap of 10 offers, the ordering being The Bonus Stack's own order, and the exact fields each result carries (amount, main requirement, deadline, last-verified date, page link, apply link). It also warns that state eligibility limits many offers, which is behavioral context no annotation conveys.

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?

Front-loaded with the definition, then examples, then a call-to-action pointer — nothing is buried. It runs as one long paragraph and the four example questions, while useful, make it denser than necessary; light structuring would improve scanability.

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

Completeness5/5

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

Seven optional parameters with full schema coverage, and with no output schema the description takes on the return-value burden itself, listing the per-offer fields and the result cap. Combined with the state-eligibility caveat and the get_bonus hand-off, an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the schema already carries parameter meaning; the description adds rationale for the state parameter (many offers are state-limited) and the examples implicitly connect intents like 'no direct deposit' and 'no monthly fee' to direct_deposit and filters. It does not explain sort values or the portal account type, leaving those to the schema.

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?

States a specific verb and resource ('Find current US bank account bonuses') and then defines the resource precisely as cash paid for opening a checking, savings or fintech account and meeting requirements. It also separates itself from the sibling get_bonus by scoping this tool to discovery and that one to a single offer's full terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives four concrete user-question phrasings that map onto this tool, an explicit prerequisite-style instruction ('Always pass the person's state when you know it, because many offers are limited to certain states'), and routes the agent to get_bonus when full terms of one offer are needed.

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