Skip to main content
Glama

The Bonus Stack

How long a bank takes to pay its bonus

get_payout_timeline
Read-onlyIdempotent

See how long a bank takes to pay a bonus after the account is opened, from community reports and the offer's own terms. Use it for 'how long until Chase pays the bonus' or 'when will my Wells Fargo bonus post'.

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

Input Schema

NameRequiredDescriptionDefault
bankYesThe bank's name, such as Chase or Wells Fargo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so safety is covered. The description earns credit for disclosing data provenance, community reports blended with the offer's own terms, which hints at reliability and freshness expectations, but it says nothing about what happens when no reports exist or how current the data is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the core purpose front-loaded before the example phrasings. Nothing is repeated or padded.

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 lookup with no output schema, the definition conveys what the answer represents (expected payout timing). It leaves minor gaps on handling unknown banks or empty community-report coverage, which an agent might need.

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 'bank' parameter is already documented with examples in the schema. The description's sample queries echo the same usage without adding format, matching, or edge-case guidance beyond it; baseline 3 applies.

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 and resource: how long a bank takes to pay a bonus after account opening. The timing focus is plainly distinct from bonus-amount or direct-deposit siblings, though no sibling is named as a contrast.

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 when-to-use triggers in the form of two sample user questions ('how long until Chase pays the bonus', 'when will my Wells Fargo bonus post'). It stops short of exclusions or naming an alternative to use for a different question type.

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