Skip to main content
Glama

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. The OCC issued its final implementing rule on 2026-10-21 (Bulletin 2026-50, 12 CFR Part 15, effective 2027-01-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/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.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").

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": "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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description earns credit for adding execution semantics beyond that: deterministic compute, server-side vs browser delegation via the compute parameter, transient processing with no storage or logging, and an AP2 artifact carrying execution_hash. The main deduction is that the core rule sentence is truncated mid-word ('registered-examiner presen...'), leaving one behavioral requirement unreadable.

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 wall of mixed content: a regulatory citation dump with the full Bulletin number and CFR part, compute-mode plumbing, provenance boilerplate, an fv-status path and hash, a 24-item output field list, and a truncation cut off mid-sentence. Load-bearing facts are buried rather than front-loaded, and the output enumeration is largely filler given the tool's core purpose.

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 compute-heavy compliance node with no output schema and nested policy_parameters, the description does supply the regulatory framework, deadline, compute behavior, provenance artifact and the output field inventory. What is missing is the resolution against the conformance sibling and MiCA counterpart, plus the truncated end of the rules summary, so an agent cannot be fully confident it picked the right checker.

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 100%, so the schema already documents compute, parent_hashes, parent_tool_ids and policy_parameters. The description does add some meaning beyond the schema, notably that dual_control(2) requires distinct CEO and CFO identities for certifying_officers, tying the FDIC NPR and OCG SPEC.md §27.3 to a specific input. It does not explain the relationship between parent_hashes and parent_tool_ids, nor the required-key semantics of policy_parameters, so the baseline 3 holds.

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 description states a specific verb and resource: it lints an extracted monthly reserve disclosure against GENIUS Act S.394 §4 dimensions (composition eligibility, tenor, custody, CEO/CFO certification gate). That is far more than a restatement of the name. However it never distinguishes itself from the near-identically named sibling check_genius_reserve_disclosure_conformance, nor from check_mica_reserve_disclosure, so an agent cannot resolve the collision from this text alone.

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 is implied through the regulatory framing (monthly reporting obligation, deadline 2027-01-18, >$50B issuers needing PCAOB audit) and the downstream note that output feeds ptg-01-ap2-prompt-template-generator. There is also a concrete constraint: 'Use synthetic or anonymised inputs only.' But there is no explicit when-to-use versus when-not, and no routing to the conformance or MiCA reserve siblings that overlap this scope.

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.