Skip to main content
Glama

The Bonus Stack

What counts as a direct deposit at a bank

check_direct_deposit
Read-onlyIdempotent

Check which transfers a bank counts as a direct deposit for its bonus, from community reports. Use it for questions like 'does Zelle count as direct deposit at Chase', 'what triggers the direct deposit requirement at SoFi' or 'can I use a transfer from Fidelity instead of a paycheck'. Pass the bank, and the transfer source if the person named one. Returns each reported source with whether recent reports say it worked, how many reports there are and the newest report date. These are other people's reports, not the bank's promise.

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": {
      "bank": "<bank>"
    },
    "name": "check_direct_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankYesThe bank's name, such as Chase, SoFi or Wells Fargo.
transfer_sourceNoThe transfer the person asked about, such as Zelle, Fidelity, Venmo or a paycheck.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 focuses on what annotations can't say: the return contents (each reported source, worked/not, report count, newest report date) and the important provenance caveat that these are user reports, not the bank's guarantee. What's missing is behavior for the no-reports or unknown-bank case.

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 core purpose, then examples, then return shape, then the trust caveat in a natural order. It runs slightly long with three quoted example questions, but each one demonstrates a distinct query pattern (named bank+source, trigger-based, substitution-based) rather than repeating itself.

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?

With no output schema, the description correctly takes on the burden of describing return fields and their reliability. For a two-parameter read tool with full annotation coverage, an agent has everything needed: purpose, when to call, what to pass, and what comes back.

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 documents both fields well. The description still adds meaning beyond it by clarifying that transfer_source should be passed only 'if the person named one', framing it as a conditional lookup key rather than a required filter, and by giving the bank-vs-source distinction the examples rely on.

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: checking which transfers a bank counts as a direct deposit, specifically for bonus requirements, sourced from community reports. The scope is narrow enough to distinguish it from find_bonuses, get_bonus, or get_payout_timeline without opening any other 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?

Gives three concrete example questions ('does Zelle count as direct deposit at Chase', 'can I use a transfer from Fidelity instead of a paycheck') that map directly onto the trigger conditions, plus instruction on when to supply the optional source. It doesn't explicitly exclude a case or name a sibling alternative, so it falls short of a 5.

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