Skip to main content
Glama

AINumbers Fintech Intelligence Suite

TMPG Fails-Charge Recompute

recompute_tmpg_fails_charge
Read-onlyIdempotent

TMPG Fails-Charge Recompute: OpenChainGraph compute node (compliance_control). 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-575-tmpg-fails-charge-recompute.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: Recomputes the NY Fed Treasury Market Practices Group fails-charge claim a buyer presents to a failing seller on a UST, agency, or agency-MBS settlement fail: charge = max(0, 3% minus the caller-declared reference rate) / 360 x par amount x days failed, per the published trading practice (2016 re... Outputs: clause_note, decision, determinations, diff_tolerance_minor, fail_count, rejected_inputs, scope_note, total_claimed_charge_minor, total_recomputed_charge_minor, verdict. Output schema: call describe_tool("recompute_tmpg_fails_charge").

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

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: diff_tolerance_minor, fails. 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: diff_tolerance_minor, fails. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "diff_tolerance_minor": {},
      +  "fails": {
      +    "type": "array"
      +  }
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "clause_note": {
      -      "type": "string"
      -    },
      -    "decision": {
      -      "properties": {
      -        "execution_state": {
      -          "type": "string"
      -        },
      -        "reason": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "determinations": {
      -      "items": {
      -        "properties": {
      -          "claimed_charge_minor": {
      -            "type": "integer"
      -          },
      -          "days_failed": {
      -            "type": "integer"
      -          },
      -          "delta_minor": {
      -            "type": "integer"
      -          },
      -          "fail_id": {
      -            "type": "string"
      -          },
      -          "par_amount_minor": {
      -            "type": "integer"
      -          },
      -          "rate_diff_bps": {
      -            "type": "integer"
      -          },
      -          "recomputed_charge_minor": {
      -            "type": "integer"
      -          },
      -          "reference_rate_bps": {
      -            "type": "integer"
      -          },
      -          "verdict": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "diff_tolerance_minor": {
      -      "type": "integer"
      -    },
      -    "fail_count": {
      -      "type": "integer"
      -    },
      -    "rejected_inputs": {
      -      "type": "array"
      -    },
      -    "scope_note": {
      -      "type": "string"
      -    },
      -    "total_claimed_charge_minor": {
      -      "type": "integer"
      -    },
      -    "total_recomputed_charge_minor": {
      -      "type": "integer"
      -    },
      -    "verdict": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "clause_note": {
      +      "type": "string"
      +    },
      +    "decision": {
      +      "properties": {
      +        "execution_state": {
      +          "type": "string"
      +        },
      +        "reason": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "determinations": {
      +      "items": {
      +        "properties": {
      +          "claimed_charge_minor": {
      +            "type": "integer"
      +          },
      +          "days_failed": {
      +            "type": "integer"
      +          },
      +          "delta_minor": {
      +            "type": "integer"
      +          },
      +          "fail_id": {
      +            "type": "string"
      +          },
      +          "par_amount_minor": {
      +            "type": "integer"
      +          },
      +          "rate_diff_bps": {
      +            "type": "integer"
      +          },
      +          "recomputed_charge_minor": {
      +            "type": "integer"
      +          },
      +          "reference_rate_bps": {
      +            "type": "integer"
      +          },
      +          "verdict": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "diff_tolerance_minor": {
      +      "type": "integer"
      +    },
      +    "fail_count": {
      +      "type": "integer"
      +    },
      +    "rejected_inputs": {
      +      "type": "array"
      +    },
      +    "scope_note": {
      +      "type": "string"
      +    },
      +    "total_claimed_charge_minor": {
      +      "type": "integer"
      +    },
      +    "total_recomputed_charge_minor": {
      +      "type": "integer"
      +    },
      +    "verdict": {
      +      "type": "string"
      +    }
      +  },
      +  "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 cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description adds genuinely new behavior: deterministic execution, server-side vs browser delegation rules for compute:auto/server/browser, transient non-retained input processing, and export of an AP2 artifact carrying execution_hash for chain provenance. It also discloses a useful caveat that the FV-status receipt is a snapshot rather than a subscription. The merely stylistic boilerplate around these points costs it the top mark.

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 large share of the text does not help an agent select or call the tool: the compute-node preamble, a marketing URL, and a 64-character FV-status hash with a sentence about offline verification. The useful content (scope, formula, compute modes, outputs) is interleaved rather than front-loaded, forcing a reader to scan past noise to find the purpose.

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?

The tool has four parameters with a nested object and no output schema; the description compensates by enumerating the return fields (clause_note, verdict, total_recomputed_charge_minor, rejected_inputs, etc.) and by explaining compute modes and provenance chaining. What remains missing is the expected shape of the 'fails' array and the meaning of diff_tolerance_minor, which is named as required in the schema but never explained in the text.

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 four parameters are already documented and the baseline is 3. The description adds formula context that gives meaning to the policy_parameters payload ('charge = max(0, 3% minus the caller-declared reference rate) / 360 x par amount x days failed'), but it never explains the structure of individual fails entries, which is the only genuinely underspecified part (the schema declares 'fails' as an untyped array).

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 'Summary:' sentence gives a precise verb and resource: 'Recomputes the NY Fed Treasury Market Practices Group fails-charge claim a buyer presents to a failing seller on a UST, agency, or agency-MBS settlement fail', plus the exact charge formula. That is specific enough to separate it from siblings such as predict_settlement_fail or compute_trid_tolerance_cure. The drawback is placement: the definition opens with 'OpenChainGraph compute node (compliance_control)' boilerplate, so the actual purpose is buried mid-paragraph.

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 implied by the scenario described (a buyer presenting a fails-charge claim against a failing seller) and by the constraint 'Use synthetic or anonymised inputs only'. There is no explicit when-to-use / when-not-to-use guidance and no named alternative for adjacent cases such as predicting a settlement fail or recomputing a different fee type. The compute-mode paragraph explains how to invoke, not whether to invoke.

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.