Skip to main content
Glama

yax_forecast_cash_flow

Read-onlyIdempotent

Generate week-by-week cash flow forecasts across base, optimistic, and pessimistic scenarios. Returns inflow/outflow projections and a Filecoin-anchored report for planning or lending.

Instructions

Generates a week-by-week cash flow forecast across base, optimistic, and pessimistic scenarios. Returns inflow/outflow projections and a Filecoin-anchored report CID for board or lender use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
horizon_weeksNoNumber of weeks to forecast. Defaults to 13 (one quarter).
scenariosNoScenarios to model: ['base', 'optimistic', 'pessimistic']. Defaults to all three.
include_arNoInclude accounts-receivable projections. Defaults to true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoTrue if forecast succeeded.
run_idNoRun ID for receipt retrieval.
forecastNoWeek-by-week cash flow projection array with inflows, outflows, and net position per scenario.
report_cidNoFilecoin CID of the anchored forecast report.

Implementation Reference

  • The forecastCashFlow SDK method that calls 'yax_forecast_cash_flow' via JSON-RPC. This is the typed client-side invocation of the MCP tool.
    forecastCashFlow(args: { horizon_days?: number; scenarios?: string[] } = {}): Promise<GenericToolResponse> {
      return this.call("yax_forecast_cash_flow", args as Record<string, unknown>);
  • The tool name 'yax_forecast_cash_flow' is registered/used in the SDK's call method. No server-side registration code was found in this codebase — the actual handler lives on the remote YieldAgentX402 MCP server at https://api.yieldagentx402.app/mcp.
    forecastCashFlow(args: { horizon_days?: number; scenarios?: string[] } = {}): Promise<GenericToolResponse> {
      return this.call("yax_forecast_cash_flow", args as Record<string, unknown>);
Behavior4/5

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

Consistent with annotations (readOnlyHint, idempotentHint). Adds Filecoin-anchored report detail. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no unnecessary words. Efficiently conveys purpose and key outputs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be described. Sufficient context for a read-only forecasting tool with no side effects.

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 coverage is 100%, so description adds little beyond schema. It mentions 'week-by-week' and scenario names, but these are already in schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it generates a week-by-week cash flow forecast across base, optimistic, and pessimistic scenarios, and returns inflow/outflow projections and a CID. Differentiates from siblings like yax_audit_compliance and yax_monitor_churn_risk, which are unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Mentions use for 'board or lender use', providing context. No explicit when-not-to-use or alternatives, but sibling tools are diverse and not direct competitors.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fabio662/yieldagentx402-sdks'

If you have feedback or need assistance with the MCP directory API, please join our Discord server