Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

ASC 340-40 Commission Amortization

amortize_asc606_commissions
Read-onlyIdempotent

ASC 340-40 Commission Amortization: OpenChainGraph compute node (compliance_mandate). 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. Consumes upstream artifacts from: art-266-reconcile-commission-statement. Open at: https://ainumbers.co/chaingraph/art-265-amortize-asc606-commissions.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("amortize_asc606_commissions").

Input Schema

TableJSON 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". See the tool's manifest for field names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "amortization_period_months": {
-      "type": "integer"
-    },
-    "annual_amortization": {
-      "type": "integer"
-    },
-    "apply_expedient": {
-      "type": "boolean"
-    },
-    "asc340_40_compliant": {
-      "type": "boolean"
-    },
-    "carrying_amount": {
-      "type": "integer"
-    },
-    "impairment_flag": {
-      "type": "boolean"
-    },
-    "incremental_cost_test_passed": {
-      "type": "boolean"
-    },
-    "monthly_amortization": {
-      "type": "integer"
-    },
-    "not_legal_advice": {
-      "type": "string"
-    },
-    "pii_note": {
-      "type": "string"
-    },
-    "regulatory_basis": {
-      "type": "string"
-    },
-    "renewal_treatment": {
-      "type": "string"
-    },
-    "table_source": {
-      "type": "string"
-    },
-    "table_version": {
-      "type": "string"
-    },
-    "total_amortization_periods": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "amortization_period_months": {
+      "type": "integer"
+    },
+    "annual_amortization": {
+      "type": "integer"
+    },
+    "apply_expedient": {
+      "type": "boolean"
+    },
+    "asc340_40_compliant": {
+      "type": "boolean"
+    },
+    "carrying_amount": {
+      "type": "integer"
+    },
+    "impairment_flag": {
+      "type": "boolean"
+    },
+    "incremental_cost_test_passed": {
+      "type": "boolean"
+    },
+    "monthly_amortization": {
+      "type": "integer"
+    },
+    "not_legal_advice": {
+      "type": "string"
+    },
+    "pii_note": {
+      "type": "string"
+    },
+    "regulatory_basis": {
+      "type": "string"
+    },
+    "renewal_treatment": {
+      "type": "string"
+    },
+    "table_source": {
+      "type": "string"
+    },
+    "table_version": {
+      "type": "string"
+    },
+    "total_amortization_periods": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  3. 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 bar is lower, and the description adds genuine behavior: inputs are processed transiently and not stored or logged, a browser delegation URL is returned for compute:'browser'/gpu:true, and an AP2 artifact with execution_hash is exported for provenance. These are real traits beyond the annotations.

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 front-loaded, but the body is padded with generic OpenChainGraph scaffolding, a full FV-status URL and 64-char hash, and repeated compute-mode text that duplicates the schema, all before any task-specific guidance. Much of the length does not earn its place.

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 4-param compliance compute node with no output schema, the description covers storage, compute modes, provenance, and upstream chaining, and defers output structure to describe_tool. The significant remaining gap is the policy_parameters object, whose field names are deferred to an external manifest, leaving core input semantics unstated.

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's compute-mode explanation largely restates the schema, and it adds little on parent_hashes ordering or the opaque policy_parameters object. 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 opening states a specific verb+resource: amortization of ASC 340-40 commissions, and the title confirms the domain. However, it never distinguishes itself from near-siblings like build_amortization_schedule, compute_deterministic_amortization_schedule, or reconcile_commission_statement, so a sibling-differentiation gap remains.

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?

It gives an input constraint ('Use synthetic or anonymised inputs only') and names the upstream artifact (art-266-reconcile-commission-statement), which implies context. But it never states when to prefer this tool over the other commission/amortization siblings, so usage is only implied.

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