Skip to main content
Glama

Bancadia MCP

list_business_checking

Compare US business checking accounts. Returns up to limit rows (default 7, max 20), total_matches, next_offset (pass as offset). Requested fields always appear (false = not offered, null = not published); an unrequested missing field = not offered or not published. A *_condition value qualifies the value next to it. Give application_url to the user exactly as returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_business_checking"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNomonthly_fee_asc, monthly_fee_desc, apy_max_desc, apy_default_desc, minimum_opening_deposit_asc, free_transactions_desc, product_name_asc
limitNoRows per page
fieldsNoReplaces the defaults (institution_name, product_name, monthly_fee, minimum_opening_deposit, insurance_type, apy_max, apy_default, free_transactions_per_month). Also: institution_display_name, institution_website_url, institution_type, monthly_fee_waiver_condition, entity_types_accepted, available_states, target_industries, target_business_profiles, deposit_insurance_limit, deposit_insurance_extended, deposit_insurance_extended_limit, per_transaction_fee_after_limit, outgoing_domestic_wire_fee, free_domestic_wires_per_month, outgoing_international_wire_fee, incoming_domestic_wire_fee, incoming_international_wire_fee, cash_deposit_available, cash_deposit_fee_per_100, monthly_cash_deposit_limit, interest_bearing, apy_tiers, rtp_supported, rtp_network, physical_debit_card_available, virtual_cards_available, corporate_card_available, atm_fee_reimbursement, atm_fee_reimbursement_limit, atm_network, sub_accounts_supported, check_writing_available, bill_pay_available, remote_deposit_capture, positive_pay_available, overdraft_protection_available, overdraft_line_of_credit_available, ach_debit_block_available, multicurrency_support, daily_debit_limit, accounting_integration_available, tax_integration_available, expense_integration_available, plan_tiers, promotions, last_modified, last_verified, is_verified
offsetNoRows to skip
apy_minNoMin apy_max (best case), decimal: 0.02 = 2%
min_limitsNo>= n on any plan. Keys: sub_accounts, free_cash_deposit_usd, free_wires, monthly_cash_limit_usd
rtp_networkNofednow, rtp_network, both or none
rank_profilesNoRANK ONLY, never excludes (as rank_industries). Values: early_stage_startup, vc_backed, bootstrapped_solopreneur, established_smb, high_growth, side_hustle
rtp_supportedNoAny real-time rail
insurance_typeNofdic, ncua or uninsured
min_insured_usdNoMin total FDIC/extended coverage, USD; unpublished extended amounts go to possible_matches
monthly_fee_maxNoMax monthly fee, USD
rank_industriesNoRANK ONLY, never excludes: orders by number of matching segment tags, after any explicit sort. Values: ecommerce, retail_storefront, restaurant_food_service, content_creator_solopreneur, professional_services, real_estate, healthcare_practice, construction_trades, trucking_logistics, agriculture, saas_tech, nonprofit, small_business_digital_first
available_statesNoTwo-letter codes; must serve ALL
integrations_allNoIntegrates with ALL (same slugs)
integrations_anyNoIntegrates with ANY: quickbooks, xero, stripe (aliases like qbo ok) or built-in native-ar (invoicing/AR), native-ap (bill mgmt/AP)
interest_bearingNo
bill_pay_availableNo
has_active_promotionNotrue: only current promotions (rows include them); false: none. Some banks only
entity_types_acceptedNoMust accept ALL: llc, s_corp, c_corp, sole_prop, partnership, nonprofit
free_transactions_minNoMin free transactions per month
multicurrency_supportNo
cash_deposit_availableNo
remote_deposit_captureNoMobile check deposit
sub_accounts_supportedNoSub-accounts with own controls, cards or account numbers (not earmark buckets)
check_writing_availableNo
virtual_cards_availableNo
corporate_card_availableNo
savings_buckets_supportedNoEarmark-only buckets (taxes, payroll); no own cards or controls. May overlap sub_accounts_supported
tax_integration_availableNo
minimum_opening_deposit_maxNoMax opening deposit, USD
expense_integration_availableNo
physical_debit_card_availableNo
accounting_integration_availableNoThird-party accounting sync only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / accounting_integration_available / description
      Added value: +"Third-party accounting sync only"
    • changedInput schema / properties / apy_min / description
      Previous value: -"Min best-case rate (apy_max), decimal: 0.02 = 2%. apy_default is the standard rate"New value: +"Min apy_max (best case), decimal: 0.02 = 2%"
    • changedInput schema / properties / has_active_promotion / description
      Previous value: -"true: only current promotions (rows include promotions); false: none. Recorded for some banks only"New value: +"true: only current promotions (rows include them); false: none. Some banks only"
    • changedInput schema / properties / integrations_all / description
      Previous value: -"Integrates with ALL"New value: +"Integrates with ALL (same slugs)"
    • changedInput schema / properties / integrations_any / description
      Previous value: -"Integrates with ANY, e.g. quickbooks, xero, stripe (aliases like qbo work)"New value: +"Integrates with ANY: quickbooks, xero, stripe (aliases like qbo ok) or built-in native-ar (invoicing/AR), native-ap (bill mgmt/AP)"
    • changedInput schema / properties / min_insured_usd / description
      Previous value: -"Min total FDIC/extended coverage in USD; extended coverage with unpublished amount goes to possible_matches"New value: +"Min total FDIC/extended coverage, USD; unpublished extended amounts go to possible_matches"
    • changedInput schema / properties / min_limits / description
      Previous value: -"Value >= n on any plan. Keys: sub_accounts, free_cash_deposit_usd, free_wires, monthly_cash_limit_usd"New value: +">= n on any plan. Keys: sub_accounts, free_cash_deposit_usd, free_wires, monthly_cash_limit_usd"
    • changedInput schema / properties / rank_industries / description
      Previous value: -"RANK ONLY, never excludes: orders by how many of these segments a bank is tagged for, after any explicit sort. Values: ecommerce, retail_storefront, restaurant_food_service, content_creator_solopreneur, professional_services, real_estate, healthcare_practice, construction_trades, trucking_logistics, agriculture, saas_tech, nonprofit, small_business_digital_first"New value: +"RANK ONLY, never excludes: orders by number of matching segment tags, after any explicit sort. Values: ecommerce, retail_storefront, restaurant_food_service, content_creator_solopreneur, professional_services, real_estate, healthcare_practice, construction_trades, trucking_logistics, agriculture, saas_tech, nonprofit, small_business_digital_first"
    • changedInput schema / properties / rank_profiles / description
      Previous value: -"RANK ONLY, never excludes (ordering as rank_industries). Values: early_stage_startup, vc_backed, bootstrapped_solopreneur, established_smb, high_growth, side_hustle"New value: +"RANK ONLY, never excludes (as rank_industries). Values: early_stage_startup, vc_backed, bootstrapped_solopreneur, established_smb, high_growth, side_hustle"
    • changedInput schema / properties / savings_buckets_supported / description
      Previous value: -"Earmark-only buckets (taxes, payroll); no own cards or controls. May also have sub_accounts_supported"New value: +"Earmark-only buckets (taxes, payroll); no own cards or controls. May overlap sub_accounts_supported"
    • changedInput schema / properties / sub_accounts_supported / description
      Previous value: -"Sub-accounts with own controls, cards or account numbers (not earmark-only buckets)"New value: +"Sub-accounts with own controls, cards or account numbers (not earmark buckets)"
  2. Changed2 schema fields changed
    • addedInput schema / properties / savings_buckets_supported
      Added value: +{
      +  "description": "Earmark-only buckets (taxes, payroll); no own cards or controls. May also have sub_accounts_supported",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / sub_accounts_supported / description
      Added value: +"Sub-accounts with own controls, cards or account numbers (not earmark-only buckets)"
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden well: it discloses pagination behavior, default/max limit, total_matches, next_offset handling, field-value semantics for false/null, condition-value qualification, and exact application_url display. It stops short of explicitly stating read-only behavior, rate limits, or error handling.

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?

The description is front-loaded and compact, with every sentence carrying operational information. Dense clauses are separated with semicolons and punctuation, but there is no wasted wording.

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 34-parameter read/search tool with no annotations and no output schema, the description covers the essential return-shape behavior, pagination, field interpretation, and application_url handling. It still lacks high-level guidance on filter combination and when the comparison tool should be selected.

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 71%, so the schema already documents many parameters. The description adds meaningful semantics beyond the schema for limit (default 7, max 20), offset (pass next_offset), and fields behavior, though it does not clarify most of the 34 filter parameters.

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?

The description states a specific verb and resource: comparing US business checking accounts. It is clear what the tool is for, though it does not explicitly distinguish itself from sibling tools.

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

Usage Guidelines2/5

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

The description implies the tool is used for comparing business checking accounts but gives no explicit when-to-use guidance, no exclusions, and no alternative-tool routing. Operational instructions such as pagination are present, but selection guidance is absent.

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.