Skip to main content
Glama

The Bonus Stack

Get one bank bonus in full

get_bonus
Read-onlyIdempotent

Get the full details of one bank bonus: every requirement step, the bonus amount or tiers, the deadline, the fees and how to avoid them, who is eligible and in which states, whether the bank does a hard credit pull, when the bonus is paid, and the apply link. Use it after find_bonuses, or when a person names a bank or an account, such as 'the Chase Total Checking bonus' or 'is the SoFi bonus still live'. Pass bonus_id from find_bonuses, or a bank or account name.

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

Input Schema

NameRequiredDescriptionDefault
nameNoA bank or account name, such as Chase Total Checking or SoFi, when there is no bonus_id.
stateNoThe person's state, to add the conditions that apply there.
bonus_idNoThe bonus_id from find_bonuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's main added value is disclosing the shape of the returned detail set and that state-specific conditions get folded in. It does not cover what happens on an ambiguous or unmatched name (e.g., which bonus is returned when 'Chase' matches several), which is the one behavioral gap worth noting.

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 purpose sentence is front-loaded and dense with concrete return fields rather than filler, and the second sentence handles routing and parameter sourcing. The long comma-separated enumeration is efficient, though slightly list-heavy; nothing in the text is genuinely redundant.

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?

With no output schema, the description correctly should explain what comes back, and it does so comprehensively, plus it explains how to supply the identifier. It is nearly complete, with the only shortfall being ambiguity handling for name-based lookup and no explicit statement that the tool returns an error or multiple candidates when a name is imprecise.

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 already 100%, including the state enum and maxLengths, so the baseline is 3. The description adds the useful routing fact that bonus_id comes from find_bonuses and that a bank or account name may be passed instead, but it never explains how the state parameter changes the lookup, leaving the schema to carry that meaning entirely.

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 a specific verb and resource ('Get the full details of one bank bonus') and then enumerates exactly what 'full details' means: requirement steps, amounts/tiers, deadline, fees, eligibility by state, credit-pull policy, payout timing, and apply link. That enumeration makes it clearly distinguishable from a list-style sibling like find_bonuses.

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?

It states the trigger conditions explicitly ('after find_bonuses, or when a person names a bank or an account') and gives concrete utterances ('the Chase Total Checking bonus', 'is the SoFi bonus still live'). The only minor omission is that it never states a when-not condition, but the alternative is named and the routing rule is unambiguous.

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