AINumbers Fintech Intelligence Suite

GENIUS Act Reserve Attestation Pre-Check

precheck_reserve_attestation

Read-onlyIdempotent

GENIUS Act Reserve Attestation Pre-Check: OpenChainGraph compute node (attestation_mandate). Regulatory deadline: 2027-01-01 (GENIUS Act effective ≤ January 2027; monthly reserve reports + annual PCAOB audit (>$50B issuers); FDIC NPRM April 2026). 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: ptg-01-ap2-prompt-template-generator. Open at: https://ainumbers.co/chaingraph/art-06-genius-act-reserve-attestation.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("precheck_reserve_attestation").

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: -{
-  "additionalProperties": false,
-  "properties": {
-    "aicpa_2025_score_pct": {
-      "type": "number"
-    },
-    "applicable_deadline": {
-      "type": "string"
-    },
-    "asset_results": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "eligibility": {
-            "type": "string"
-          },
-          "has_fail": {
-            "type": "boolean"
-          },
-          "issues": {
-            "type": "array"
-          },
-          "pct": {
-            "type": "number"
-          },
-          "type": {
-            "type": "string"
-          },
-          "usd": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "eligibility",
-          "has_fail",
-          "issues",
-          "pct",
-          "type",
-          "usd"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "attestation_readiness_determination": {
-      "enum": [
-        "FAIL",
-        "INDETERMINATE",
-        "PASS"
-      ],
-      "type": "string"
-    },
-    "conditional_assets_usd": {
-      "type": "number"
-    },
-    "coverage_ratio_pct": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "failing_dimensions": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "detail": {
-            "type": "string"
-          },
-          "dim": {
-            "type": "string"
-          },
-          "ref": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "detail",
-          "dim",
-          "ref"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "prohibited_assets_usd": {
-      "type": "number"
-    },
-    "regulatory_framework": {
-      "type": "string"
-    },
-    "reserve_shortfall_usd": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "total_liabilities_usd": {
-      "type": "number"
-    },
-    "total_reserves_usd": {
-      "type": "number"
-    },
-    "warnings": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "aicpa_2025_score_pct",
-    "applicable_deadline",
-    "asset_results",
-    "attestation_readiness_determination",
-    "conditional_assets_usd",
-    "coverage_ratio_pct",
-    "failing_dimensions",
-    "prohibited_assets_usd",
-    "regulatory_framework",
-    "reserve_shortfall_usd",
-    "total_liabilities_usd",
-    "total_reserves_usd",
-    "warnings"
-  ],
-  "type": "object",
-  "x_schema_provenance": "derived via node scripts/check-output-schema-coverage.mjs --derive (CCPP-FIX-ART06-1, 2026-09-08) — §2.7 truth maintenance: declared output_schema re-aligned to the kernel's fixture-observed output after the explicit-absence fix (null coverage/shortfall, INDETERMINATE state)"
-}New value: +null

Changed15 schema fields changedSep 9, 2026

addedOutput schema / additionalProperties
```
Added value: +false
```
changedOutput schema / properties / aicpa_2025_score_pct / type
```
Previous value: -"integer"New value: +"number"
```

addedOutput schema / properties / asset_results / items

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "eligibility": {
+      "type": "string"
+    },
+    "has_fail": {
+      "type": "boolean"
+    },
+    "issues": {
+      "type": "array"
+    },
+    "pct": {
+      "type": "number"
+    },
+    "type": {
+      "type": "string"
+    },
+    "usd": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "eligibility",
+    "has_fail",
+    "issues",
+    "pct",
+    "type",
+    "usd"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / attestation_readiness_determination / enum
```
Added value: +[
+  "FAIL",
+  "INDETERMINATE",
+  "PASS"
+]
```
changedOutput schema / properties / conditional_assets_usd / type
```
Previous value: -"integer"New value: +"number"
```

changedOutput schema / properties / coverage_ratio_pct / type

Previous value: -"integer"New value: +[
+  "null",
+  "number"
+]

addedOutput schema / properties / failing_dimensions / items / additionalProperties
```
Added value: +false
```
addedOutput schema / properties / failing_dimensions / items / required
```
Added value: +[
+  "detail",
+  "dim",
+  "ref"
+]
```
changedOutput schema / properties / prohibited_assets_usd / type
```
Previous value: -"integer"New value: +"number"
```

changedOutput schema / properties / reserve_shortfall_usd / type

Previous value: -"integer"New value: +[
+  "null",
+  "number"
+]

changedOutput schema / properties / total_liabilities_usd / type
```
Previous value: -"integer"New value: +"number"
```
changedOutput schema / properties / total_reserves_usd / type
```
Previous value: -"integer"New value: +"number"
```

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / required

Added value: +[
+  "aicpa_2025_score_pct",
+  "applicable_deadline",
+  "asset_results",
+  "attestation_readiness_determination",
+  "conditional_assets_usd",
+  "coverage_ratio_pct",
+  "failing_dimensions",
+  "prohibited_assets_usd",
+  "regulatory_framework",
+  "reserve_shortfall_usd",
+  "total_liabilities_usd",
+  "total_reserves_usd",
+  "warnings"
+]

addedOutput schema / x_schema_provenance

Added value: +"derived via node scripts/check-output-schema-coverage.mjs --derive (CCPP-FIX-ART06-1, 2026-09-08) — §2.7 truth maintenance: declared output_schema re-aligned to the kernel's fixture-observed output after the explicit-absence fix (null coverage/shortfall, INDETERMINATE state)"

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "aicpa_2025_score_pct": {
+      "type": "integer"
+    },
+    "applicable_deadline": {
+      "type": "string"
+    },
+    "asset_results": {
+      "type": "array"
+    },
+    "attestation_readiness_determination": {
+      "type": "string"
+    },
+    "conditional_assets_usd": {
+      "type": "integer"
+    },
+    "coverage_ratio_pct": {
+      "type": "integer"
+    },
+    "failing_dimensions": {
+      "items": {
+        "properties": {
+          "detail": {
+            "type": "string"
+          },
+          "dim": {
+            "type": "string"
+          },
+          "ref": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "prohibited_assets_usd": {
+      "type": "integer"
+    },
+    "regulatory_framework": {
+      "type": "string"
+    },
+    "reserve_shortfall_usd": {
+      "type": "integer"
+    },
+    "total_liabilities_usd": {
+      "type": "integer"
+    },
+    "total_reserves_usd": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedJun 19, 2026

addedInput schema / properties / compute

Added value: +{
+  "description": "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.",
+  "enum": [
+    "auto",
+    "server",
+    "browser"
+  ],
+  "type": "string"
+}

removedInput schema / properties / inputs

Removed value: -{
-  "additionalProperties": {},
-  "description": "Simulation parameters for this tool's input fields. See the tool's embedded manifest for field names.",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}

addedInput schema / properties / policy_parameters

Added value: +{
+  "additionalProperties": {},
+  "description": "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.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

AddedJun 13, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely useful behavior beyond that: inputs are processed transiently and not stored or logged, compute:'browser' returns a delegation URL instead of results, gpu:true nodes always delegate, and an AP2 artifact with execution_hash is exported for chain provenance. This is meaningful disclosure for a compute node. It stops short of 5 because failure/error behavior and rate or size limits are unstated.

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

Conciseness2/5

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

The text is a dense run-on mixing regulatory-deadline trivia ('GENIUS Act effective <= January 2027; FDIC NPRM April 2026'), a documentation URL, and a long FV-status commit hash that has no bearing on tool selection or invocation. The genuinely useful sentences (compute modes, transient processing, artifact export) are buried mid-paragraph rather than front-loaded. It is over-sized relative to the value delivered.

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?

There is no output schema, yet the description points to describe_tool for it and does at least note that an AP2 artifact with execution_hash is returned and that output feeds ptg-01-ap2-prompt-template-generator. However, with a nested policy_parameters object and no field documentation beyond 'see the manifest', an agent lacks enough to construct a meaningful call. Adequate but with clear gaps.

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% and the schema already documents compute, parent_hashes, parent_tool_ids and policy_parameters, so the description largely repeats the compute-mode semantics rather than extending them. Crucially it offers no help on policy_parameters contents, deferring to 'See the tool's manifest for field names', which leaves the primary decision inputs opaque. Baseline 3 is appropriate.

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 description identifies the tool as a 'GENIUS Act Reserve Attestation Pre-Check' compute node for the 'attestation_mandate' domain, which gives a verb-ish resource and a regulatory frame. But it never says what is actually checked or what the pre-check decides, and it does nothing to distinguish itself from close siblings such as check_genius_reserve_disclosure, check_genius_reserve_disclosure_conformance, or verify_proof_of_reserves_consistency. The regulatory deadline boilerplate crowds out whatever minimal purpose statement exists.

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?

The only usage instruction is operational ('Use synthetic or anonymised inputs only') plus a compute-mode decision, neither of which tells an agent when to pick this tool over the sibling GENIUS/reserve-disclosure checks. There is no when-to-use, when-not-to-use, or prerequisite information (e.g. what inputs must exist before a pre-check is meaningful). An agent must infer applicability from the title alone.

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.

GENIUS Act Reserve Attestation Pre-Check

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources