Skip to main content
Glama

get_nist_ai_rmf_requirements

Read-only

Use when conducting an AI risk management gap assessment, building board-level AI governance documentation, preparing for a model risk examination, or aligning an AI program with federal regulatory expectations. NIST AI RMF 1.0 is the US federal standard for AI risk management — adopted by reference in the Executive Order on Safe AI and aligned with Federal Reserve SR 26-2, OCC model risk guidance, and FDIC requirements. Returns all four functions (GOVERN, MAP, MEASURE, MANAGE) with categories, subcategories, and implementation guidance. Example: GOVERN function requires board-level AI policy, documented accountability structures, and AI risk culture assessment — the first control examiners check in a model risk review. Source: NIST AI RMF 1.0. $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_nist_ai_rmf_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
function_filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-destructive, so the description's job is to add context — and it does: it names the source standard, states that all four functions with categories/subcategories/guidance are returned, and discloses a $0.50 per-call cost. It does not describe response shape or size, but that is a minor gap for a read-only lookup.

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-loads the when-to-use triggers, then the standard's provenance, then the return contents and price. Mostly earns its length, though the 'first control examiners check' example is promotional filler rather than decision-relevant information.

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 no output schema, the description correctly carries the burden of saying what comes back (four functions, categories, subcategories, implementation guidance) plus source and cost. The only unfilled hole is how function_filter interacts with the 'returns all four' claim.

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 coverage is 0% for the single parameter, and the description never explains that function_filter narrows the result to one of the four functions — it only says the tool 'returns all four functions,' which an agent could read as contradicting the filter's existence. The enum values are self-describing, so the gap is real but not severe.

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 a specific resource (NIST AI RMF 1.0 requirements across GOVERN/MAP/MEASURE/MANAGE) and its scope. It distinguishes itself from siblings implicitly by naming NIST/federal framing versus state (Colorado) or EU regimes, but never names an alternative directly.

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 four concrete triggering scenarios (gap assessment, board governance docs, model risk exam prep, federal alignment), which is well above typical. It stops short of explicit exclusions, e.g. 'use get_eu_ai_act_coverage instead when the client operates in the EU.'

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