Skip to main content
Glama
Sign In

Bankrolled.ai Agent Hub

by ai.bankrolled
OverviewDiscussionsAdmin

Official Money Limit Lookup

money_fact
Read-onlyIdempotent

Get an official, dated personal-finance limit: deposit insurance (FDIC, FSCS, CDIC, AU FCS, NZ DCS) or contribution limits and allowances (UK ISA, Lifetime ISA, Junior ISA, pension annual allowance, Personal Savings Allowance; US 401k + catch-ups, IRA, Roth IRA, HSA; Canada TFSA, RRSP, FHSA; Australia super concessional/non-concessional caps; NZ KiwiSaver government contribution). Use instead of memory when a user asks "how much is protected" or "how much can I contribute". Pass q as plain English ("fdic limit joint account", "isa allowance") or a fact_key from pricing_list. Returns fact, source {name,url}, as_of, jurisdiction, cite. Free, no key. Unknown -> not_in_catalog (never guesses).

Input Schema

NameRequiredDescriptionDefault
qYesPlain-English question or fact_key, e.g. "fscs deposit protection limit" or "us_401k_limit_2026".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / examples
      Previous value: -[
-  "fdic insurance limit",
-  "fscs deposit protection limit",
-  "isa annual contribution limit",
-  "401k contribution limit",
-  "tfsa contribution limit",
-  "us_fdic_joint_accounts"
-]New value: +[
+  "fdic insurance limit",
+  "fscs deposit protection limit",
+  "isa annual contribution limit",
+  "401k contribution limit",
+  "tfsa contribution limit",
+  "us_fdic_joint_accounts",
+  "hsa contribution limit",
+  "rrsp contribution limit",
+  "super concessional contributions cap",
+  "lifetime isa limit"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / q / description
      Previous value: -"A fact_key (exact) or a short search query. fact_keys: us_fdic_standard_limit, us_fdic_joint_accounts, uk_fscs_deposit_limit, uk_fscs_temporary_high_balance, ca_cdic_deposit_limit, au_fcs_deposit_limit, nz_dcs_deposit_limit, uk_isa_annual_limit, us_401k_limit_2026, us_401k_catch_up_2026, us_roth_ira_limit_2026, ca_tfsa_limit_2026."New value: +"Plain-English question or fact_key, e.g. \"fscs deposit protection limit\" or \"us_401k_limit_2026\"."
    • changedInput schema / properties / q / examples
      Previous value: -[
-  "us_fdic_standard_limit",
-  "us_fdic_joint_accounts",
-  "uk_fscs_deposit_limit",
-  "uk_fscs_temporary_high_balance",
-  "ca_cdic_deposit_limit",
-  "au_fcs_deposit_limit",
-  "nz_dcs_deposit_limit",
-  "uk_isa_annual_limit",
-  "us_401k_limit_2026",
-  "us_401k_catch_up_2026",
-  "us_roth_ira_limit_2026",
-  "ca_tfsa_limit_2026",
-  "fdic insurance limit",
-  "fdic coverage joint accounts",
-  "fscs deposit protection limit",
-  "fscs temporary high balance",
-  "cdic deposit insurance limit",
-  "australia fcs deposit guarantee",
-  "new zealand deposit compensation",
-  "isa annual contribution limit",
-  "401k contribution limit",
-  "401k catch up contribution",
-  "roth ira contribution limit",
-  "tfsa contribution limit"
-]New value: +[
+  "fdic insurance limit",
+  "fscs deposit protection limit",
+  "isa annual contribution limit",
+  "401k contribution limit",
+  "tfsa contribution limit",
+  "us_fdic_joint_accounts"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations: discloses the return fields (fact, source{name,url}, as_of, jurisdiction, cite), states the failure mode ('Unknown -> not_in_catalog (never guesses)'), and notes it is free with no key. No contradiction with annotations; only missing element is any rate/pagination detail, which is largely moot for a lookup.

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 capability and the usage rule; the long jurisdiction list is dense but genuinely informative for routing. Slight bloat in the enumerated allowance types, though each earns its place by signaling catalog breadth.

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 still describes the return payload and the not-found behavior. For a single-parameter read-only lookup, nothing an agent needs in order to call it correctly is missing.

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% and already has examples, so the baseline would be 3. The description adds real meaning by framing q as either free-form plain English or a fact_key sourced externally from pricing_list, which the schema does not say.

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+resource ('Get an official, dated personal-finance limit') and enumerates the exact categories of limits covered across five jurisdictions. An agent can distinguish it from scheme_lookup and pricing_list without opening any schema.

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?

Explicit trigger given: 'Use instead of memory when a user asks "how much is protected" or "how much can I contribute"'. It also names the alternative input source (a fact_key from pricing_list), giving the agent both when-to-use and where-else-to-look guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bankrolled.ai Agent Hub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources