Skip to main content
Glama

AINumbers Fintech Intelligence Suite

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/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Computes ASC 340-40-25-4 practical expedient (contract_term_months <= 12 -> expense immediately, apply_expedient=true) and full straight-line amortization schedules for longer-term capitalized incremental costs of obtaining a contract under ASC 606. Outputs: amortization_period_months, annual_amortization, apply_expedient, asc340_40_compliant, carrying_amount, impairment_flag, incremental_cost_test_passed, monthly_amortization, not_legal_advice, pii_note, regulatory_basis, renewal_treatment, table_source, table_version, total_amortization_periods. Output schema: call describe_tool("amortize_asc606_commissions").

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

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". 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\". Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "amortization_period_override_months": {},
      +  "contract_term_months": {},
      +  "impairment_indicators": {},
      +  "incremental_cost": {},
      +  "renewal_commensurate": {},
      +  "renewal_cost": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. 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
  4. 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"
      +}
  5. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description goes meaningfully beyond them: deterministic compute, server-vs-browser delegation via the compute mode, transient processing with no retention or logging, synthetic-inputs-only guidance, and an AP2 artifact carrying execution_hash for provenance. That is real operational context an agent would otherwise have to guess. It loses a point because much of this is templated boilerplate repeated across the family rather than specific to this computation.

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?

A single dense paragraph that blends three unrelated registers: compute/provenance boilerplate, a hashed FV-status URL, and the actual accounting rule. The 15-item flat output list ('amortization_period_months, annual_amortization, ...') consumes space without types or meaning, and the substantive ASC 340-40 rule is buried mid-paragraph rather than front-loaded.

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?

With no output schema, listing outputs is justified, and the domain rule plus upstream artifact are covered. However, it never says which policy_parameters are needed for a valid call (0 required params), what happens with missing inputs, or what the impairment and incremental-cost tests actually evaluate, leaving the core decision inputs under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds genuine meaning the schema lacks: policy_parameters' nested keys are undocumented in the schema, and the description supplies the decision rule (contract_term_months <= 12 implies apply_expedient=true and immediate expensing) plus mentions that unknown keys are refused. That maps contract_term_months and impairment_indicators to observable outputs, exceeding what the flat schema conveys.

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 names a specific verb and regulatory resource: it 'Computes ASC 340-40-25-4 practical expedient ... and full straight-line amortization schedules' for capitalized incremental costs under ASC 606. That is specific enough to separate it from generic siblings like build_amortization_schedule or recompute_lease_schedule_asc842_ifrs16, though it never explicitly names a sibling it is not.

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 via the upstream chaining note ('Consumes upstream artifacts from: art-266-reconcile-commission-statement'), which tells an agent where it sits in a workflow. There is no explicit statement of when to choose this over the other amortization or commission-reconciliation tools, and no exclusions.

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.