AINumbers Fintech Intelligence Suite

FR 2052a Inflow/Outflow Bucket Classifier

compute_fr2052a_inflow_outflow_classification

Read-onlyIdempotent

FR 2052a Inflow/Outflow Bucket Classifier: OpenChainGraph compute node (regulatory_reporting). 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. Open at: https://ainumbers.co/chaingraph/art-437-fr2052a-inflow-outflow-classifier.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: FR 2052a complex-institution liquidity monitoring filing-layer kernel, scoped to the inflow/outflow section: product/maturity-bucket classification against a caller-supplied Appendix IV-style boundary table (versioned policy input, not hardcoded), intercompany elimination (excluded from external... Outputs: boundary_table_version, elimination_total_musd, form_2052a, note, override_count, override_missing_reason_count, row_count, rows, total_inflow_musd, total_net_musd, total_outflow_musd. Output schema: call describe_tool("compute_fr2052a_inflow_outflow_classification").

Input 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". Required: boundary_table_version, bucket_boundaries, rows. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed3 schema fields changedOct 19, 2026

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: boundary_table_version, bucket_boundaries, rows. Unknown keys are refused."

addedInput schema / properties / policy_parameters / properties

Added value: +{
+  "boundary_table_version": {},
+  "bucket_boundaries": {},
+  "rows": {}
+}

removedInput schema / properties / policy_parameters / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "boundary_table_version": {
-      "type": "string"
-    },
-    "elimination_total_musd": {
-      "type": "integer"
-    },
-    "form_2052a": {
-      "items": {
-        "properties": {
-          "bucket": {
-            "type": "string"
-          },
-          "inflow_musd": {
-            "type": "integer"
-          },
-          "net_musd": {
-            "type": "integer"
-          },
-          "outflow_musd": {
-            "type": "integer"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "note": {
-      "type": "string"
-    },
-    "override_count": {
-      "type": "integer"
-    },
-    "override_missing_reason_count": {
-      "type": "integer"
-    },
-    "row_count": {
-      "type": "integer"
-    },
-    "rows": {
-      "items": {
-        "properties": {
-          "amount_musd": {
-            "type": "integer"
-          },
-          "bucket": {
-            "type": "string"
-          },
-          "flow_type": {
-            "type": "string"
-          },
-          "is_intercompany": {
-            "type": "boolean"
-          },
-          "maturity_days": {
-            "type": "integer"
-          },
-          "override_applied": {
-            "type": "boolean"
-          },
-          "override_reason_code": {
-            "type": "string"
-          },
-          "row_id": {
-            "type": "string"
-          },
-          "table_bucket": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total_inflow_musd": {
-      "type": "integer"
-    },
-    "total_net_musd": {
-      "type": "integer"
-    },
-    "total_outflow_musd": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "boundary_table_version": {
+      "type": "string"
+    },
+    "elimination_total_musd": {
+      "type": "integer"
+    },
+    "form_2052a": {
+      "items": {
+        "properties": {
+          "bucket": {
+            "type": "string"
+          },
+          "inflow_musd": {
+            "type": "integer"
+          },
+          "net_musd": {
+            "type": "integer"
+          },
+          "outflow_musd": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "override_count": {
+      "type": "integer"
+    },
+    "override_missing_reason_count": {
+      "type": "integer"
+    },
+    "row_count": {
+      "type": "integer"
+    },
+    "rows": {
+      "items": {
+        "properties": {
+          "amount_musd": {
+            "type": "integer"
+          },
+          "bucket": {
+            "type": "string"
+          },
+          "flow_type": {
+            "type": "string"
+          },
+          "is_intercompany": {
+            "type": "boolean"
+          },
+          "maturity_days": {
+            "type": "integer"
+          },
+          "override_applied": {
+            "type": "boolean"
+          },
+          "override_reason_code": {
+            "type": "string"
+          },
+          "row_id": {
+            "type": "string"
+          },
+          "table_bucket": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_inflow_musd": {
+      "type": "integer"
+    },
+    "total_net_musd": {
+      "type": "integer"
+    },
+    "total_outflow_musd": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

AddedJul 24, 2026

TDQS

B3.2/5.0

Behavior4/5

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

With readOnlyHint/idempotentHint already declared, the description still adds real behavioral context: deterministic execution, transient processing with no storage or logging, server-side vs browser-delegation routing, gpu:true forcing delegation, and AP2 artifact export with execution_hash for chain provenance. Nothing here contradicts the annotations. It falls short of 5 because it never says what the caller gets back beyond a bare output-name list.

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?

Structure is poor: it opens with redundant platform boilerplate ('OpenChainGraph compute node' twice), then the purpose, then a raw URL, a full FV-status receipt URL and 64-char hash, and finally a sentence that cuts off with an ellipsis. The single most decision-relevant line is neither front-loaded nor complete.

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 nested-object, no-output-schema tool it covers input policy semantics, compute routing, privacy posture and an explicit list of returned fields, which is broadly adequate. But the truncated elimination clause leaves a core behavior (how intercompany items are excluded from external totals) unexplained, and the instruction to call describe_tool for the output schema offloads work the description could have done.

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 the required policy_parameters keys, and the description largely repeats the compute-mode text verbatim. The one genuine addition is framing the boundary table as a 'versioned policy input, not hardcoded', which explains why boundary_table_version matters. Baseline 3 applies.

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 does eventually state a specific verb and resource: product/maturity-bucket classification of FR 2052a inflow/outflow items against a caller-supplied Appendix IV-style boundary table, plus intercompany elimination. It even differentiates scope ('scoped to the inflow/outflow section') from the many other FR 2052a / liquidity siblings. It loses a point because the opening sentence is a name/title restatement and the substantive summary is buried and truncated mid-clause ('excluded from external...').

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 guidance concerns execution mode ('auto' vs 'browser') and input hygiene ('Use synthetic or anonymised inputs only'). There is no statement of when to pick this tool over the adjacent liquidity/intercompany tools (compute_intercompany_elimination_netting, compute_intraday_liquidity_monitoring, map_call_report_schedule_rc), nor any precondition for supplying a boundary table version.

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.

FR 2052a Inflow/Outflow Bucket Classifier

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources