Skip to main content
Glama

Bancadia MCP

search_facts

Full-text search of fee and feature details across banks (e.g. 'zelle'). Best snippets per bank with application_url. Terms are ANDed; 'or', "quotes", -exclude work; long queries with no hit fall back to any-term matching (relaxed: true).

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": {
      "query": "<query>"
    },
    "name": "search_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
slugsNoOnly these slugs; misses go in no_match
topicNofees, payment_rails, cash_handling, cards_and_atm, online_banking, fraud_protection, account_management, platform_integrations or other
per_bankNoSnippets per bank, 1-5, default 2
max_banksNoBanks returned, 1-20, default 10
max_charsNoSnippet length, 40-600, default 220

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavior burden and does disclose the result shape ('best snippets per bank with application_url') and a non-obvious fallback: long queries with no hits relax to any-term matching and set relaxed: true. It does not discuss rate limits or that this is a read-only lookup, though search semantics imply it.

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?

Three short sentences, front-loaded with purpose before query syntax detail, with no filler. It is dense and telegraphic -- 'relaxed: true' references an output field never explained -- but every sentence carries information.

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 6-parameter search tool with no output schema, the description covers purpose, query syntax, and partial result structure (snippets, application_url, relaxed flag). Remaining gaps are minor since the schema documents the filtering and sizing parameters itself.

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 83%, so the schema already documents most parameters, establishing a baseline of 3. The description adds genuine meaning for the undocumented query parameter (AND semantics, 'or', quotes, -exclude, relaxed fallback) but says nothing about slugs, topic, per_bank, max_banks, or max_chars beyond the schema.

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 ('Full-text search of fee and feature details across banks') with an example query, which is clearly distinct from structured siblings like fees_by_type or get_listing. It stops short of naming any sibling to explicitly route the agent, so it is clear but not fully differentiating.

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 guidance is present but aimed at query construction (ANDing, 'or', quotes, -exclude, relaxed fallback) rather than tool selection. There is no explicit statement of when to choose this over fees_by_type or get_listing, leaving that inference to the agent.

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.