Skip to main content
Glama

get_bank_counterparty_diligence

Read-only

Use when diligencing a bank or financial institution counterparty before onboarding, funding, or transaction approval. Fans in bank regulatory benchmark, AML regulatory benchmark, OCC enforcement actions, credit union peer benchmark, and CFPB complaint intelligence — degrading per-section on source_unavailable. Input institution_name (required). $3.00 USDC per call.

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": {
      "institution_name": "<institution_name>"
    },
    "name": "get_bank_counterparty_diligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
aml_focusNo
asset_size_tierNo
institution_nameYes
institution_typeNo
credit_union_asset_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior, and the description adds two things annotations cannot: the per-section graceful degradation on source_unavailable (so partial results are expected) and a $3.00 USDC price per call. It does not say whether a degraded call is still billed in full or what the response shape looks like, which is the remaining gap for a paid aggregation call.

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?

Four sentences, front-loaded with the trigger condition and then fan-in scope, degradation behavior, and price — each sentence carries decision-relevant information. "Input institution_name (required)" mildly repeats the schema, the only low-value clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-source paid aggregator, the description covers the essentials of cost and partial-failure behavior, but it leaves four enum parameters completely undocumented and gives no sense of what sections the response contains or how per-section degradation is surfaced to the caller. Adequate to invoke, not sufficient to invoke well.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, and the description only mentions institution_name as required. The four enum parameters (aml_focus, asset_size_tier, institution_type, credit_union_asset_tier) are never explained — no defaults, no guidance on which tier vocabulary applies to which institution_type, and no note on how credit_union_asset_tier interacts with asset_size_tier. With zero schema coverage the description was the only place to compensate and it did not.

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 names a specific activity (counterparty diligence on a bank/financial institution) and explicitly lists the five intelligence sources it fans in, so an agent can tell it is an aggregator rather than a single-source tool. It stops short of naming the sibling component tools (get_bank_regulatory_benchmark, get_aml_regulatory_benchmark, get_cfpb_complaint_intelligence) as alternatives, so the boundary is implied rather than stated.

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?

"Use when diligencing ... before onboarding, funding, or transaction approval" gives concrete trigger contexts that map to real decision points. There are no exclusions or routing rules telling the agent when to prefer a narrower sibling tool over this composite, which keeps it from a 5.

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