AINumbers Fintech Intelligence Suite

NIST AI RMF Function Mapper

map_nist_ai_rmf_functions

Read-onlyIdempotent

NIST AI RMF Function Mapper: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Output feeds: art-175-gpai-code-of-practice-conformance, art-314-traiga-safe-harbor-pack-builder. Open at: https://ainumbers.co/chaingraph/art-174-nist-ai-rmf-function-mapper.html FV-status (published/proven/still-trusted for this spec): /fv-status/8498d0819c941fdb731f9e10f5d93ee929026919cb111a42149821b48b5ac180.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Output schema: call describe_tool("map_nist_ai_rmf_functions").

Input Schema

TableJSON Schema

Name	Required	Description
`compute`	No	Compute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
`parent_hashes`	No	execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
`parent_tool_ids`	No	tool_id values matching parent_hashes, in the same order.
`policy_parameters`	No	Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". See the tool's manifest for field names.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "all_gaps": {
-      "type": "array"
-    },
-    "controls_present": {
-      "type": "integer"
-    },
-    "coverage_band": {
-      "type": "string"
-    },
-    "function_coverage": {
-      "properties": {
-        "GOVERN": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        },
-        "MANAGE": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        },
-        "MAP": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        },
-        "MEASURE": {
-          "properties": {
-            "gaps": {
-              "type": "array"
-            },
-            "present": {
-              "type": "integer"
-            },
-            "score": {
-              "type": "integer"
-            },
-            "total": {
-              "type": "integer"
-            }
-          },
-          "type": "object"
-        }
-      },
-      "type": "object"
-    },
-    "overall_coverage": {
-      "type": "integer"
-    },
-    "total_controls": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "all_gaps": {
+      "type": "array"
+    },
+    "controls_present": {
+      "type": "integer"
+    },
+    "coverage_band": {
+      "type": "string"
+    },
+    "function_coverage": {
+      "properties": {
+        "GOVERN": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "MANAGE": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "MAP": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "MEASURE": {
+          "properties": {
+            "gaps": {
+              "type": "array"
+            },
+            "present": {
+              "type": "integer"
+            },
+            "score": {
+              "type": "integer"
+            },
+            "total": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "overall_coverage": {
+      "type": "integer"
+    },
+    "total_controls": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedJun 27, 2026

TDQS

B3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context: deterministic execution, server-vs-browser compute modes, transient processing with no storage or logging, and an AP2 artifact export with execution_hash for provenance. The synthetic-input warning is a useful operational constraint, though much of the compute-node wording is generic boilerplate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is padded with compute-infrastructure boilerplate, a raw URL, and a long FV-status receipt path that add bulk without helping tool selection. Some sentences (compute modes, transient processing) earn their place; others do not.

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 4-parameter, nested-object tool with no output schema, the description covers the operational behavior and provenance artifact but delegates output shape to describe_tool and never explains the domain mapping itself. It is adequate operationally but incomplete on what the tool actually computes.

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 the schema already documents compute mode and the parent_hashes/tool_ids chaining fields. The description restates compute:'auto' behavior but adds no field names or syntax for the nested policy_parameters object ('See the tool's manifest'), so it does not exceed the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title and opening line identify it as a NIST AI RMF function mapper and an OpenChainGraph compliance_mandate compute node, distinguishing it from AI-governance siblings like assess_ai_act_conformity. However, the body never states what is being mapped to the NIST AI RMF functions or in what form, so the actual purpose remains vague beyond the name.

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?

There is no explicit when-to-use or when-not guidance and no named alternative sibling. The 'Output feeds' line hints at downstream usage context and 'Use synthetic or anonymised inputs only' is a usage constraint, but neither tells the agent when to select this over other compliance-mapping tools.

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

All AINumbers Fintech Intelligence Suite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

NIST AI RMF Function Mapper

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources