Skip to main content
Glama

get_occ_enforcement_actions

Read-only

Use when assessing regulatory risk for a national bank or federal thrift before a merger, acquisition, partnership, correspondent banking relationship, or vendor engagement. Returns active and historical OCC enforcement actions — formal agreements, consent orders, cease-and-desist orders, and civil money penalties — the same records OCC examiners pull during supervisory reviews. Example: First National Bank of Springfield — formal agreement active since March 2022 requiring BSA/AML program overhaul, independent compliance consultant, and quarterly progress reports to OCC — agreement not yet terminated, elevates acquisition risk materially. Source: OCC Enforcement Actions — official supervisory records. $0.50 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_occ_enforcement_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
institution_nameYesBank or thrift name (e.g. First National Bank of Springfield)

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 cover the safety profile (readOnlyHint, non-destructive, open-world), and the description adds genuinely new context: results span active and historical actions, provenance is OCC supervisory records, and the cost is $0.50 USDC per call. It omits matching behavior for institution names and how results are ordered or paginated, keeping it below a 5.

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?

The usage condition is front-loaded and the record-type list follows immediately, so the reader gets the essentials quickly. The worked example ('First National Bank of Springfield — formal agreement active since March 2022...') is lengthy but demonstrates what a returned record looks like, so it largely earns its space.

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?

With only one parameter and no output schema, the description carries the burden of explaining returns, and it does so by naming the action types and illustrating a representative record. Diagnosis-level details such as name-matching tolerance or result limits are missing but are not essential to correct invocation.

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 description coverage is 100% and the single parameter is already documented with the same example institution name used in the description, so the prose adds little parameter-level meaning. At most it implies the name should be a national bank or federal thrift, which marginally narrows 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?

States a specific verb and resource ('Returns active and historical OCC enforcement actions') and enumerates the record types returned — formal agreements, consent orders, cease-and-desist orders, civil money penalties. Naming OCC plus 'national bank or federal thrift' clearly separates it from sibling enforcement tools such as get_ftc_enforcement_history and get_osha_enforcement.

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?

Gives an explicit trigger context: use before a merger, acquisition, partnership, correspondent banking relationship, or vendor engagement. It does not name a sibling alternative or state a when-not condition (e.g., use get_cfpb_complaint_intelligence for consumer-complaint risk), so it falls short of full routing guidance.

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