Skip to main content
Glama

BankRegReports

Enforcement Feed

enforcement
Read-only

Industry-wide regulatory enforcement-action feed. (Source: Federal regulators.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enforcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 100, max 500).
agencyNoRegulator: occ, fdic, frb, or sec_8k.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful provenance (data comes from federal regulators), but says nothing about freshness cadence, historical coverage window, or whether results are paginated.

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?

Two compact sentences with the resource and scope front-loaded and the source information parenthesized. There is no filler wording to trim.

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 two-optional-parameter read-only feed with full schema coverage and annotations covering safety, the definition is minimally viable. It still leaves an agent guessing about time coverage, default agency behavior, and how to page beyond the row limit.

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%, so both the limit and agency parameters are documented in the schema, establishing a baseline of 3. The description contributes no additional meaning, such as what happens when agency is omitted (all regulators?) or how to handle more than the page cap.

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 the resource precisely: an industry-wide regulatory enforcement-action feed sourced from federal regulators. 'Industry-wide' hints at scope versus the agency-specific siblings (enforcement_actions, ncua_enforcement), but no sibling is named, so an agent must infer the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance at all. The reader is not told when to pick this over enforcement_actions or ncua_enforcement, nor whether the caller should filter by agency for targeted queries.

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