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/8498d0819c941fdb731f9e10f5d93ee929026919cb111a42149821b48b5ac180.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Output schema: call describe_tool("compute_fr2052a_inflow_outflow_classification").

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

C2.7/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, so this text earns credit for adding non-obvious behavior: default server-side execution on Workers for gpu:false nodes, browser delegation for gpu:true, transient processing with no storage/logging/retention, and AP2 artifact export with execution_hash for chain provenance. The data-retention disclosure is genuinely useful for a compliance-domain tool and is not derivable from annotations.

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?

Front-loading is poor: the first sentence is a name restatement, followed by long stretches of boilerplate about compute binding, FV-status receipts, an HTML URL, and a 64-hex hash. The 'Output schema: call describe_tool(...)' pointer is useful, but a large fraction of the text is provenance infrastructure rather than tool selection information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-input compliance classifier with no output schema, the description omits the most important thing: what inputs the policy_parameters object expects and what the bucket output looks like. The describe_tool pointer partially mitigates this, but an agent still cannot construct a meaningful call from the definition alone.

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 baseline is 3 even with no parameter discussion. The description does sharpen the compute enum semantics slightly, but it explicitly defers the decisive input surface to 'the tool's manifest', leaving policy_parameters (the actual decision function input, a nested open object) unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description largely restates the name ('FR 2052a Inflow/Outflow Bucket Classifier: OpenChainGraph compute node') and then pivots to infrastructure boilerplate about compute modes and provenance artifacts. It never says what the classification does or what decision it renders (bucket assignment? inflow vs outflow determination?). An agent cannot tell this apart from the many other classify_* siblings on the basis of the text.

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 is operational ('compute:"auto"' vs 'browser') and a data-hygiene warning to use synthetic inputs. There is no statement of when this classifier applies versus alternatives like classify_settlement_finality or classify_sco60_exposure, and no prerequisites such as which regulatory schema version or return form it targets.

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