Skip to main content
Glama

Stratalize Healthcare

Get Bank Counterparty Diligence

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

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: per-section graceful degradation on 'source_unavailable' and a $3.00 USDC per-call cost, both of which affect whether and how an agent invokes it. It does not state latency or how partial results are marked in the response, which keeps it below 5.

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?

Three tight sentences, front-loaded with the usage trigger, followed by the aggregation scope, degradation behavior, required input, and cost. No filler and nothing repeated from the annotations.

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 composite aggregation tool with no output schema, the description covers what it fans in, how partial failure is handled, the required input, and the price — enough for an agent to decide correctly. The remaining hole is guidance on the four optional enum parameters, which leaves an agent guessing whether they are worth setting.

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%, so the description carries the full burden for five parameters, yet it only mentions institution_name as required. The four enum parameters (aml_focus, asset_size_tier, institution_type, credit_union_asset_tier) get no explanation of how they narrow which intelligence sections are returned — a material gap given the enums drive the fan-in scope.

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 opens with a specific verb and resource ('diligencing a bank or financial institution counterparty') and then enumerates exactly what the tool aggregates: bank regulatory benchmark, AML regulatory benchmark, OCC enforcement actions, credit union peer benchmark, and CFPB complaint intelligence. This fan-in list makes it distinguishable from the sibling point-solution tools like get_bank_regulatory_benchmark, get_aml_regulatory_benchmark, and get_cfpb_complaint_intelligence.

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?

It gives concrete triggering contexts ('before onboarding, funding, or transaction approval'), which is stronger than most definitions. It stops short of explicitly naming when to pick a narrower sibling instead, but the fan-in enumeration implicitly tells the agent this is the composite option covering those sources.

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