Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Cash Forecast Accuracy Scoring

score_cash_forecast_accuracy
Read-onlyIdempotent

Cash Forecast Accuracy Scoring: OpenChainGraph compute node (analytics_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-258-parse-camt053-reconciliation, art-261-test-hedge-effectiveness. Open at: https://ainumbers.co/chaingraph/art-263-score-cash-forecast-accuracy.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: Scores treasury cash forecast accuracy per AFP Cash Forecasting Survey 2024 benchmarks. Outputs: afp_benchmark_tiers, by_horizon, not_legal_advice, overall_accuracy_tier, overall_bias_pct, overall_mape_pct, persistent_sign_periods, pii_note, regulatory_basis, skipped_zero_actual, table_source, table_version, timing_bias_detected, total_observations. Output schema: call describe_tool("score_cash_forecast_accuracy").

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

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: forecasts. 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: forecasts. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "forecasts": {
      +    "type": "array"
      +  }
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "afp_benchmark_tiers": {
      -      "type": "string"
      -    },
      -    "by_horizon": {
      -      "properties": {
      -        "T+1": {
      -          "properties": {
      -            "accuracy_tier": {
      -              "type": "string"
      -            },
      -            "bias_pct": {
      -              "type": "integer"
      -            },
      -            "mape_pct": {
      -              "type": "integer"
      -            },
      -            "n": {
      -              "type": "integer"
      -            }
      -          },
      -          "type": "object"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "not_legal_advice": {
      -      "type": "string"
      -    },
      -    "overall_accuracy_tier": {
      -      "type": "string"
      -    },
      -    "overall_bias_pct": {
      -      "type": "integer"
      -    },
      -    "overall_mape_pct": {
      -      "type": "integer"
      -    },
      -    "persistent_sign_periods": {
      -      "type": "integer"
      -    },
      -    "pii_note": {
      -      "type": "string"
      -    },
      -    "regulatory_basis": {
      -      "type": "string"
      -    },
      -    "skipped_zero_actual": {
      -      "type": "integer"
      -    },
      -    "table_source": {
      -      "type": "string"
      -    },
      -    "table_version": {
      -      "type": "string"
      -    },
      -    "timing_bias_detected": {
      -      "type": "boolean"
      -    },
      -    "total_observations": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "afp_benchmark_tiers": {
      +      "type": "string"
      +    },
      +    "by_horizon": {
      +      "properties": {
      +        "T+1": {
      +          "properties": {
      +            "accuracy_tier": {
      +              "type": "string"
      +            },
      +            "bias_pct": {
      +              "type": "integer"
      +            },
      +            "mape_pct": {
      +              "type": "integer"
      +            },
      +            "n": {
      +              "type": "integer"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "not_legal_advice": {
      +      "type": "string"
      +    },
      +    "overall_accuracy_tier": {
      +      "type": "string"
      +    },
      +    "overall_bias_pct": {
      +      "type": "integer"
      +    },
      +    "overall_mape_pct": {
      +      "type": "integer"
      +    },
      +    "persistent_sign_periods": {
      +      "type": "integer"
      +    },
      +    "pii_note": {
      +      "type": "string"
      +    },
      +    "regulatory_basis": {
      +      "type": "string"
      +    },
      +    "skipped_zero_actual": {
      +      "type": "integer"
      +    },
      +    "table_source": {
      +      "type": "string"
      +    },
      +    "table_version": {
      +      "type": "string"
      +    },
      +    "timing_bias_detected": {
      +      "type": "boolean"
      +    },
      +    "total_observations": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

B3.2/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, so the safety profile is covered. The description adds genuinely useful behavior: transient processing with no storage or logging, the requirement to use synthetic or anonymised inputs, server-vs-browser delegation semantics, and an AP2 artifact export carrying execution_hash for provenance — none of which appears in 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 definition is padded with chain-of-custody boilerplate, a raw FV-status URL and a 64-character hash before reaching the actual one-line purpose, and then dumps an unstructured list of output field names. The useful content (purpose, privacy constraint, outputs) is present but not front-loaded, and large stretches do not earn their place for an agent deciding whether to call the tool.

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 compute node with a rich four-parameter schema, the description does cover execution modes, data-handling constraints, upstream artifact consumption, artifact export and the output field inventory, so nothing critical is missing. It is weaker on the ambiguous boundary with compute_forecast_accuracy_score and leaves the output fields uninterpreted, relying on describe_tool for that.

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 explanation of compute modes largely restates the schema, and it says nothing about the shape of policy_parameters.forecasts beyond noting it is required, so baseline 3 is appropriate.

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 eventually states a specific verb and resource: 'Scores treasury cash forecast accuracy per AFP Cash Forecasting Survey 2024 benchmarks', and enumerates the outputs. However, that purpose sits several sentences deep behind generic OpenChainGraph boilerplate, and it never distinguishes itself from the near-identical sibling compute_forecast_accuracy_score, so an agent cannot confidently route between the two from the description alone.

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?

There is no when-to-use / when-not-to-use guidance and no alternative named. The compute-mode text ('auto'/'server'/'browser') explains execution mechanics rather than tool selection, and the mention of upstream artifacts (art-258, art-261) hints at chaining context but not at when this tool should be preferred over siblings.

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.