Skip to main content
Glama

The Bonus Stack

Guides to how bank bonuses work

search_guides
Read-onlyIdempotent

Find The Bonus Stack's plain-English guides: what counts as a direct deposit, whether bank bonuses are taxed, how ChexSystems works, how long to keep an account open, and each bank's direct deposit guide. Use it for how-to questions and for 'is it taxed' or 'will it hurt my credit' questions that are not about one specific offer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question or topic, such as 'are bank bonuses taxed' or 'ChexSystems'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world search, so the safety profile is fully covered. The description adds topical scope but says nothing about result format, ranking, result limits, or whether matching is keyword-based, which would help an agent set expectations.

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-loads the core action and resource, then follows with a compact topic list and a usage sentence. The topic list is long but each item earns its place by clarifying coverage boundaries; there is no 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 one-parameter, read-only search tool with no output schema, the definition supplies enough scope and routing guidance to invoke it correctly. Minor gaps around return shape and search behavior remain but are not essential for choosing and calling the tool.

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% and the single query parameter already has a description with examples. The description reinforces that the query is a question or topic and gives further example phrasings, but adds no syntax or format constraints beyond 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 ... guides') and enumerates the exact topics covered: direct deposit, taxes, ChexSystems, account duration, and per-bank direct deposit guides. It explicitly contrasts with offer-specific tools by saying it is for questions 'not about one specific offer', so an agent can distinguish it from find_bonuses or get_bonus.

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 clear when-to-use guidance for how-to questions and tax or credit-impact questions, plus a when-not-to-use clause excluding questions about a specific offer. It does not name the sibling that handles offer-specific questions, but the scope boundary is explicit enough to route correctly.

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