Skip to main content
Glama

Stratalize Intelligence

Get Model Risk Management Standards

get_model_risk_management_standards
Read-only

Use when preparing for a model risk management examination, building an SR 26-2 compliant model governance program, or assessing a financial institution's MRM framework against regulatory expectations. Returns Federal Reserve SR 26-2 and OCC requirements across development, independent validation, ongoing monitoring, and governance — with exam deficiency rates showing where institutions most commonly fail. For AI and ML models, SR 26-2 explicitly requires independent validation even for vendor-supplied models and black-box systems. Example: Documentation deficiencies are the most common exam finding at 67% of reviewed institutions — inadequate conceptual soundness documentation for credit scoring models triggers immediate MRA (Matter Requiring Attention). Source: Federal Reserve SR 26-2, OCC Bulletin 2026-13, FDIC FIL-15-2026. $0.50 USDC per call.

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": "get_model_risk_management_standards"
  }
}

Input Schema

NameRequiredDescriptionDefault
institution_typeNocommunity_bank

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 declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered; the description adds meaningful context beyond that: the underlying sources (SR 26-2, OCC Bulletin 2026-13, FDIC FIL-15-2026) and a per-call price of $0.50 USDC. What is not disclosed is the output form (full text vs. summarized requirement list) and whether results vary by institution type.

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?

Front-loaded with the when-to-use trigger, then return content, then a concrete example, then sources and price. The example is somewhat long, but each sentence (including the vendor/black-box validation note) carries substantive information rather than filler.

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?

With no output schema, the description does a fair job of describing return content (requirements by lifecycle stage plus exam deficiency rates), and it supplies source provenance. However, for a tool whose only input segments the audience, leaving institution_type unexplained leaves a real gap in what an agent needs to call it correctly.

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?

There is one parameter (institution_type) with 7 enum values, a default, and 0% schema description coverage, yet the description never mentions it. The reader cannot tell whether it filters the returned requirements, adjusts deficiency statistics, or is ignored. With a single parameter the description should explain its effect, and it does not.

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 concrete verb and resource: returns Federal Reserve SR 26-2 and OCC requirements across development, independent validation, monitoring, and governance. It is readily distinguishable from sibling tools like get_ai_regulatory_landscape or get_bank_regulatory_benchmark because it names the specific MRM regime and content scope.

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

Usage Guidelines5/5

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

Opens with an explicit 'Use when...' clause listing three concrete situations (exam prep, building an SR 26-2 governance program, assessing an existing MRM framework). An agent can decide to call this without further inference.

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