Skip to main content
Glama

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/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.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").

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

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: boundary_table_version, bucket_boundaries, rows. 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: 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"
      -}
  3. Changed1 schema field changed
    • 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
  4. Changed1 schema field changed
    • 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"
      +}
  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 read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context: deterministic execution, transient input handling with no storage or logging, an exported AP2 artifact carrying execution_hash for provenance, and the fact that the boundary table is versioned policy input rather than hardcoded. It also notes unknown keys are refused, which is a useful behavioral constraint. It stops short of describing failure modes or validation errors.

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?

Front-loaded content is the title and generic OpenChainGraph compute-node boilerplate rather than the actual function, and the domain sentence is cut off mid-word. The trailing FV-status hash, artifact URL, and unlabeled output list consume much of the text without helping an agent decide or call; significant pruning would improve 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?

No output schema exists, so listing the returned fields (total_inflow_musd, elimination_total_musd, override counts, rows, etc.) does real work. However, the truncated summary and the absence of any description of the rows/bucket_boundaries input payload shapes, override handling semantics, or error behavior leave real gaps for a nested-policy-input computation node.

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% and the compute/parent_hashes/parent_tool_ids/policy_parameters semantics are fully documented in the schema itself, so the baseline of 3 applies. The description's only added meaning is that the boundary table is caller-supplied and versioned policy input, which is helpful but already largely implied by boundary_table_version in the schema.

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 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. That is far more informative than the title restatement, but the statement is buried after boilerplate and is truncated mid-clause ("excluded from external..."), and nothing distinguishes it from nearby liquidity siblings such as compute_lcr_nsfr_leverage or compute_intraday_liquidity_monitoring.

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 only implied by the domain framing (FR 2052a filing-layer classification). The description gives a real constraint, "Use synthetic or anonymised inputs only," and explains compute-mode selection, but never says when to pick this tool over the sibling liquidity/reporting compute nodes or what prerequisites the boundary table must satisfy.

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.