Skip to main content
Glama

Bancadia MCP

by io.github.macphe22

query_business_checking

Query the Bancadia registry for business checking account products using compound filter criteria. Returns active, verified listings from financial institutions. Optionally accepts target_industries/target_business_profiles to soft-rank results toward listings built for a given business type or stage — non-matching but eligible listings are still returned, just ranked lower.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apy_minNoMinimum APY (inclusive), for interest-bearing accounts
rtp_networkNoWhich real-time payment rail is supported
rtp_supportedNoWhether real-time payments (any rail) are supported at all
insurance_typeNoDeposit insurance type
monthly_fee_maxNoMaximum monthly fee
available_statesNoReturns listings available in all specified states
interest_bearingNoWhether the account earns interest
target_industriesNoSoft-ranks results toward listings built for these business types. Does not exclude non-matching but otherwise-eligible listings.
entity_types_acceptedNoReturns listings accepting all specified entity types (e.g. llc, s_corp)
free_transactions_minNoMinimum free transactions per month
cash_deposit_availableNoWhether cash deposits are supported
sub_accounts_supportedNoWhether sub-accounts are supported
target_business_profilesNoSoft-ranks results toward listings built for this business stage/shape. Does not exclude non-matching but otherwise-eligible listings.
tax_integration_availableNoWhether the account connects to any tax-prep or tax-filing software/service
minimum_opening_deposit_maxNoMaximum minimum opening deposit
expense_integration_availableNoWhether the account connects to any expense/spend-management software
accounting_integration_availableNoWhether the account connects to any accounting software (e.g. QuickBooks, Xero)

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that only active and verified listings are returned, and that the soft-ranking parameters do not exclude non-matching listings but only lower their rank. This is meaningful behavioral context beyond what the schema provides.

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 two sentences long and front-loaded with the core purpose. The second sentence explains the notable soft-ranking behavior without unnecessary detail. Every word earns its place.

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?

The description covers the main query behavior, return scope (active/verified), and optional ranking behavior. With 17 parameters and full schema coverage, the description complements the schema well, though it does not mention pagination or default behavior when no filters are provided.

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?

The schema already documents all parameters with 100% coverage, including the soft-ranking semantics for target_industries and target_business_profiles. The tool description adds no parameter-specific details beyond the overall context, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool queries a registry for business checking products using compound filter criteria, and specifies it returns active, verified listings. This distinguishes it from the sibling get_business_checking_listing, which likely retrieves a single listing rather than querying a set.

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?

The description provides clear context for when to use the tool (querying with filters) and explicitly describes the optional soft-ranking behavior, including that non-matching listings are still returned. It does not explicitly contrast with the sibling tool, but the context is unambiguous.

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

All Bancadia MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clear, distinct role: query_business_checking returns a filtered list of listings, while get_business_checking_listing returns full details for a specific listing identified by slug. There is no overlap or ambiguity in their purposes.

Naming Consistency5/5

Both tools follow the snake_case verb_noun pattern (query_ and get_ followed by business_checking-related nouns). The verbs clearly distinguish list-level vs. detail-level operations, making the naming predictable and consistent.

Tool Count4/5

With only two tools, the server is minimal but appropriately scoped for a focused registry lookup use case. It does not feel bloated, though there is room for a few more complementary tools (e.g., list banks, compare listings) without feeling excessive.

Completeness5/5

The pair provides a complete read-only workflow: search/filter to discover listings, then retrieve full details for a chosen listing. There are no obvious missing operations for the stated purpose, as create/update/delete are not relevant to a public registry viewer.

Resources