AINumbers Fintech Intelligence Suite

GENIUS Act Monthly Reserve Disclosure Checker

check_genius_reserve_disclosure

Read-onlyIdempotent

GENIUS Act Monthly Reserve Disclosure Checker: OpenChainGraph compute node (compliance_mandate). Regulatory deadline: 2027-01-18 (GENIUS Act effective ≤ January 2027; monthly reserve composition reports required for licensed issuers; >$50B issuers subject to annual PCAOB audit. Re-verify against final-rule text on/after 2026-07-18.). 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-275-genius-reserve-disclosure-checker.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("check_genius_reserve_disclosure").

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": {
-    "applicable_deadline": {
-      "type": "string"
-    },
-    "asset_results": {
-      "type": "array"
-    },
-    "ceo_certified": {
-      "type": "boolean"
-    },
-    "cfo_certified": {
-      "type": "boolean"
-    },
-    "conditional_assets_usd": {
-      "type": "integer"
-    },
-    "coverage_ratio_pct": {
-      "type": "integer"
-    },
-    "custody_disclosed": {
-      "type": "boolean"
-    },
-    "custody_locations": {
-      "type": "array"
-    },
-    "dual_control_satisfied": {
-      "type": "boolean"
-    },
-    "examiner_name": {
-      "type": "string"
-    },
-    "failing_dimensions": {
-      "items": {
-        "properties": {
-          "detail": {
-            "type": "string"
-          },
-          "dim": {
-            "type": "string"
-          },
-          "ref": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "gate_policy": {
-      "type": "string"
-    },
-    "mom_diff": {
-      "type": "string"
-    },
-    "monthly_disclosure_determination": {
-      "type": "string"
-    },
-    "onchain_supply_check": {
-      "properties": {
-        "delta": {
-          "type": "string"
-        },
-        "match": {
-          "type": "string"
-        },
-        "note": {
-          "type": "string"
-        },
-        "onchain_supply": {
-          "type": "string"
-        },
-        "provided": {
-          "type": "boolean"
-        },
-        "reported_outstanding_tokens": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "pdf_extraction_note": {
-      "type": "string"
-    },
-    "prohibited_assets_usd": {
-      "type": "integer"
-    },
-    "registered_examiner_named": {
-      "type": "boolean"
-    },
-    "regulatory_framework": {
-      "type": "string"
-    },
-    "report_month": {
-      "type": "string"
-    },
-    "reserve_shortfall_usd": {
-      "type": "integer"
-    },
-    "total_liabilities_usd": {
-      "type": "integer"
-    },
-    "total_reserves_usd": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "applicable_deadline": {
+      "type": "string"
+    },
+    "asset_results": {
+      "type": "array"
+    },
+    "ceo_certified": {
+      "type": "boolean"
+    },
+    "cfo_certified": {
+      "type": "boolean"
+    },
+    "conditional_assets_usd": {
+      "type": "integer"
+    },
+    "coverage_ratio_pct": {
+      "type": "integer"
+    },
+    "custody_disclosed": {
+      "type": "boolean"
+    },
+    "custody_locations": {
+      "type": "array"
+    },
+    "dual_control_satisfied": {
+      "type": "boolean"
+    },
+    "examiner_name": {
+      "type": "string"
+    },
+    "failing_dimensions": {
+      "items": {
+        "properties": {
+          "detail": {
+            "type": "string"
+          },
+          "dim": {
+            "type": "string"
+          },
+          "ref": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "gate_policy": {
+      "type": "string"
+    },
+    "mom_diff": {
+      "type": "string"
+    },
+    "monthly_disclosure_determination": {
+      "type": "string"
+    },
+    "onchain_supply_check": {
+      "properties": {
+        "delta": {
+          "type": "string"
+        },
+        "match": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "onchain_supply": {
+          "type": "string"
+        },
+        "provided": {
+          "type": "boolean"
+        },
+        "reported_outstanding_tokens": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "pdf_extraction_note": {
+      "type": "string"
+    },
+    "prohibited_assets_usd": {
+      "type": "integer"
+    },
+    "registered_examiner_named": {
+      "type": "boolean"
+    },
+    "regulatory_framework": {
+      "type": "string"
+    },
+    "report_month": {
+      "type": "string"
+    },
+    "reserve_shortfall_usd": {
+      "type": "integer"
+    },
+    "total_liabilities_usd": {
+      "type": "integer"
+    },
+    "total_reserves_usd": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedJul 10, 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 and non-destructive, but the description adds genuinely useful behavior: deterministic server-side compute with kernel registration, the auto/server/browser delegation semantics, transient processing with no storage/logging/retention, the 'synthetic or anonymised inputs only' constraint, and an exported AP2 artifact carrying execution_hash. These go well beyond the annotations, though the browser-delegation return shape is only partially characterized.

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?

It is front-loaded with the title, but a large fraction of the text is metadata scaffolding (regulatory deadline dates, URL, a 64-character FV-status hash, chain-provenance boilerplate) that an agent does not need in order to select or call the tool. The operational content is buried among it.

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 parameterized compute node with no output schema, the description points to describe_tool for the output contract, which partially compensates. But the actual decision inputs live in an opaque policy_parameters object whose field names are only 'in the manifest', so an agent cannot know what to submit without an extra lookup, and the return artifact structure is unstated.

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 compute, parent_hashes, parent_tool_ids and policy_parameters are already documented in the schema; the description's compute-mode prose largely duplicates the schema's compute field. The description adds nothing about policy_parameters contents, deferring to an external manifest. Baseline 3 is appropriate when the schema carries the load.

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 GENIUS Act monthly reserve disclosure checker and a compliance_mandate compute node, so the general domain is clear. However the description never states operationally what it checks or what it evaluates beyond restating the name, and it does not distinguish itself from the near-identical sibling check_genius_reserve_disclosure_conformance. Purpose is implied rather than specified.

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 when-to-use or when-not-to-use guidance, and no routing against the very similar check_genius_reserve_disclosure_conformance or check_mica_reserve_disclosure siblings. The only usage-adjacent text is the compute-mode default and the downstream 'Output feeds' pointer, neither of which tells an agent when this tool is the right call.

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 Monthly Reserve Disclosure Checker

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources