Skip to main content
Glama

Banking Regulations

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Banking Regulation

banking_regulation
Read-onlyIdempotent

Get the full text of one banking regulation — a US Federal Reserve, OCC, FDIC, CFPB or NCUA rule codified in 12 CFR — by its citation or Regulation letter. Returns the exact regulatory wording currently in force. Answers "what does Regulation E require", "what is the Federal Reserve regulation for X", "read 12 CFR 1026.19", "the CFPB rule on X", "the OCC / FDIC regulation for X", "bank capital requirement". Forgiving input: "1026.19", "12 CFR 1026.19", "§ 217.10", "1026.19(e)" (paragraph stripped to the section), "part 1026". Fed "Regulation letters" resolve automatically: "Regulation Z" (truth in lending) -> part 1026, "Reg B" (ECOA) -> 1002, "Reg C" (HMDA) -> 1003, "Reg D" -> 204, "Reg E" (EFTA) -> 1005, "Reg O" (insider lending) -> 215, "Reg W" (affiliate transactions) -> 223, "Reg X" (RESPA) -> 1024, "Reg Y" (bank holding companies) -> 225, "Reg CC" (funds availability) -> 229, "Reg DD" (truth in savings) -> 1030, "Reg Q" / capital -> 217, plus "Volcker rule" -> 248, "CRA" -> 228, "liquidity coverage ratio" -> 249. Covers bank compliance across all of Title 12: consumer financial protection, mortgage disclosure and servicing, deposits and payments, capital and liquidity, holding-company supervision, safety and soundness. Pass a whole part or Regulation letter to get that part's section list. Example: banking_regulation({ citation: "1026.19" }) -> certain mortgage and variable-rate transactions; banking_regulation({ citation: "Regulation Z" }) -> the truth-in-lending part's section list. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
citationYesBanking-regulation citation or Regulation letter. A section: "1026.19", "12 CFR 1026.19", "§ 217.10", "1002.9", "1026.19(e)". A Regulation letter or statute name: "Regulation Z", "Reg E", "truth in lending", "HMDA", "Volcker rule". Or a whole part: "1026", "part 217" -> returns the part's section list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "citation": "Regulation Z"
+  },
+  {
+    "citation": "1026.19"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent hints; the description adds behavioral context such as forgiving input handling, paragraph stripping, and behavior for parts vs sections, which is valuable beyond the annotations.

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 description is well-structured with multiple lines and examples, front-loaded with the core purpose. Every sentence adds value, though it could be slightly more concise without losing content.

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

Completeness5/5

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

Given the single parameter, lack of output schema, and high input complexity, the description fully covers return values ('exact regulatory wording currently in force', section list for parts) and input variations, making it complete for its context.

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

Parameters4/5

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

The input schema provides 100% coverage with a detailed description for 'citation'. The tool description expands on this with extensive examples and forgiveness rules, adding significant meaning beyond the schema alone.

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 explicitly states it retrieves the full text of a single banking regulation by citation or Regulation letter, with a specific verb ('Get') and resource ('banking regulation'). It distinguishes from the sibling 'banking_regulations_search' implicitly by focusing on a single regulation versus search.

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?

The description provides clear context and multiple examples of when to use the tool (e.g., 'what does Regulation E require', 'read 12 CFR 1026.19'), but does not explicitly exclude scenarios like searching across multiple regulations, which would be better served by the sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Banking Regulations toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources