Skip to main content
Glama

Bankrolled.ai Agent Hub

Deposit Insurance Scheme Lookup

scheme_lookup
Read-onlyIdempotent

Identify a country's deposit-insurance scheme and its headline coverage (US FDIC, UK FSCS, CA CDIC, AU FCS, NZ DCS) with the regulator's URL and as_of date. country accepts ISO codes or names: US/USA, UK/GB, CA, AU, NZ. Free, no key.

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": {
      "country": "<country>"
    },
    "name": "scheme_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTopic key (default: deposit_insurance).deposit_insurance
countryYesCountry code or name: US/USA, UK/GB, CA, AU, NZ (e.g. "GB", "Canada").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country code: US, UK, CA, AU, or NZ. Example: \"CA\"."New value: +"Country code or name: US/USA, UK/GB, CA, AU, NZ (e.g. \"GB\", \"Canada\")."
    • removedInput schema / properties / country / enum
      Removed value: -[
      -  "US",
      -  "UK",
      -  "CA",
      -  "AU",
      -  "NZ"
      -]
    • addedInput schema / properties / country / examples
      Added value: +[
      +  "US",
      +  "GB",
      +  "UK",
      +  "CA",
      +  "AU",
      +  "NZ"
      +]
  2. Changed4 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO-style country code: US, UK, CA, AU, or NZ. Example: \"CA\"."New value: +"Country code: US, UK, CA, AU, or NZ. Example: \"CA\"."
    • addedInput schema / properties / country / enum
      Added value: +[
      +  "US",
      +  "UK",
      +  "CA",
      +  "AU",
      +  "NZ"
      +]
    • changedInput schema / properties / topic / description
      Previous value: -"Topic key (default: deposit_insurance). Example: \"deposit_insurance\"."New value: +"Topic key (default: deposit_insurance)."
    • addedInput schema / properties / topic / enum
      Added value: +[
      +  "deposit_insurance"
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered; the description adds value beyond that by disclosing the no-auth/free access model and the returned fields (regulator URL, as_of date). It does not say what happens for an unsupported country, which is the main remaining behavioral gap.

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?

Two tight sentences: purpose and return fields first, accepted input forms next, access note last. The 'Free, no key' clause is short and earns its place, though it could be folded more smoothly into the sentence flow.

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 carries the return-value burden and does so by naming the fields returned (scheme, headline coverage, regulator URL, as_of date). Auth and supported-country scope are covered; only the out-of-scope-country behavior is unaddressed.

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 country examples in the schema duplicate the ones in the description (US/USA, UK/GB, CA, AU, NZ), so little is added. The description also omits the topic parameter entirely, though its default makes that low-risk.

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?

Names a specific verb (identify) and resource (a country's deposit-insurance scheme) and enumerates the returns: headline coverage, regulator URL, as_of date. The named scheme list (FDIC, FSCS, CDIC, FCS, DCS) makes it unmistakable against siblings like money_fact or pricing_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the five supported jurisdictions and the 'free, no key' note, which tells an agent it can call this without credentials. However, it never states when to prefer this over cross_border_check or money_fact, nor does it define behavior outside the five listed countries.

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