Skip to main content
Glama

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely non-obvious behavior beyond that — the per-call price of $0.50 USDC, the specific source documents, and the fact that returned data includes exam deficiency rates. It stops short of describing response shape or completeness/coverage limits of the standards set.

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?

Usage triggers are front-loaded, followed by return content, a concrete example, sources, and price — a sensible order. The example sentence is long and somewhat illustrative rather than operational, but it does convey severity of findings, so little is truly wasted.

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 read-only, single-parameter lookup with no output schema, the description supplies the when, the what, a sample finding, authoritative sources, and cost. The main residual gap is how institution_type scopes or filters the returned standards.

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% for the single institution_type parameter, and the description never mentions it or explains how the institution type changes which requirements are returned. The enum values are self-evident, but the parameter's effect on output is left entirely undocumented.

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?

The description names a specific regulatory resource and enumerates the four domains covered (development, independent validation, ongoing monitoring, governance) plus deficiency-rate data, so an agent knows exactly what comes back. It does not explicitly contrast itself with nearby siblings like get_bank_regulatory_benchmark or get_ai_regulatory_landscape, which is the only thing keeping it from a 5.

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?

Three concrete triggering scenarios are given up front: exam preparation, building an SR 26-2 governance program, and assessing an existing MRM framework. There are no explicit exclusions or named alternatives for the adjacent regulatory-benchmark tools, so the agent must infer boundaries.

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