Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

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/ca4e1dca8343f788a296161f0e19712f7afb7e5eaec0431081e715a4cc34b784.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Lints an extracted monthly reserve disclosure against GENIUS Act S.394 §4: composition-category eligibility, tenor, custody locations, a dual_control(2) CEO/CFO certification gate (distinct CEO and CFO identities required, per FDIC NPR 2026-04-10 and OCG SPEC.md §27.3), registered-examiner presen... Outputs: applicable_deadline, asset_results, ceo_certified, cfo_certified, conditional_assets_usd, coverage_ratio_pct, custody_disclosed, custody_locations, dual_control_satisfied, examiner_name, failing_dimensions, gate_policy, mom_diff, monthly_disclosure_determination, onchain_supply_check, pdf_extraction_note, prohibited_assets_usd, registered_examiner_named, regulatory_framework, report_month, reserve_shortfall_usd, total_liabilities_usd, total_reserves_usd. Output schema: call describe_tool("check_genius_reserve_disclosure").

Input Schema

NameRequiredDescriptionDefault
computeNoCompute 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_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput 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". Required: assets, certifying_officers, registered_examiner_named. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / policy_parameters / description
      Previous value: -"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."New value: +"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\". Required: assets, certifying_officers, registered_examiner_named. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
+  "assets": {},
+  "certifying_officers": {},
+  "examiner_name": {},
+  "issuer_type": {},
+  "onchain_supply_check": {},
+  "outstanding_tokens_reported": {
+    "type": "number"
+  },
+  "prior_month": {},
+  "registered_examiner_named": {
+    "type": "boolean"
+  },
+  "report_month": {},
+  "token_price": {
+    "type": "number"
+  }
+}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • 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
  4. Changed1 schema field changed
    • 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"
+}
  5. Added

TDQS

A3.5/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, but the description adds genuinely non-obvious behavior: deterministic compute node, server-side Cloudflare Workers execution with a browser delegation fallback, transient processing with no storage or logging, and AP2 artifact export carrying an execution_hash with parent_hashes chaining. The dual_control(2) CEO/CFO gate and 'unknown keys are refused' are also disclosed. It stops short of describing the determination outcomes or error behavior, and the trailing truncation cuts off a behavioral bullet.

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 purpose is not front-loaded — it appears after regulatory-deadline, compute-binding, privacy, AP2 provenance, and FV-status boilerplate. The response embeds a 64-hex FV-status filename, a docs URL, a 21-field output enumeration inline, and is truncated mid-sentence ("registered-examiner presen..."), which signals mechanical concatenation rather than authored prose.

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 compensates by listing every returned field (coverage_ratio_pct, dual_control_satisfied, failing_dimensions, monthly_disclosure_determination, etc.), and it covers compute modes, provenance chaining, and data handling. What holds it below 5 is the truncation and the absence of any statement of what a pass/fail determination looks like or how this differs from its conformance sibling.

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, parent_hashes, parent_tool_ids, and policy_parameters — the description largely repeats that (compute modes, required keys) rather than adding to it. The one real addition is the dual_control(2) requirement that certifying_officers contain distinct CEO and CFO identities, which gives semantic meaning the schema's empty-object policy_parameters does not. Most other policy parameter keys are undocumented in both places.

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 Summary sentence names a specific verb and resource ("Lints an extracted monthly reserve disclosure against GENIUS Act S.394 §4") and enumerates the checked dimensions (composition eligibility, tenor, custody, dual-control certification, registered examiner), so the agent knows concretely what the tool does. It does not, however, distinguish itself from the near-identically-named sibling check_genius_reserve_disclosure_conformance, and the actual purpose statement is buried behind eight sentences of compute/FV boilerplate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied (you pass an extracted disclosure draft plus certifying officers and get a conformance determination), and it does add a real constraint — "Use synthetic or anonymised inputs only" — plus compute-mode selection guidance. But there is no explicit when-to-use / when-not / alternative-tool guidance, which is a serious omission given the sibling list contains check_genius_reserve_disclosure_conformance, check_mica_reserve_disclosure, and precheck_reserve_attestation, all plausible confusions.

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 toolsInspect
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.

Resources