Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-free-cash-flow

Free Cash Flow: Computes free cash flow as operating cash flow minus capital expenditure 🆓 5 free trial calls per signed wallet

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": "x402-free-cash-flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatingCashFlowNo
capitalExpenditureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / capitalExpenditure / description
      Removed value: -"CapitalExpenditure to process"
    • removedInput schema / properties / operatingCashFlow / description
      Removed value: -"OperatingCashFlow to process"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the computation method and hints at an auth/payment model ('signed wallet', free trial quota), which is real context, but says nothing about input format expectations, error behavior, or what the result looks like.

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

Conciseness4/5

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

Front-loaded with the tool name and a one-line definition; the formula follows immediately. The trailing trial-call promo is arguably marketing boilerplate rather than tool documentation, but it is short and does not obscure the core statement.

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 pure calculator with no output schema and no annotations, the description covers what is computed but not what comes back (raw number, formatted value) or how the two string inputs should be shaped. That leaves an agent able to understand the intent but uncertain about the call contract.

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 0%, so the schema contributes nothing beyond names and a 'string' type. The description rescues the semantics by naming both operands and their arithmetic relationship, but it gives no format guidance (plain number vs. currency string, sign conventions for capex), which is the main risk with two untyped string inputs.

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?

States a specific verb (computes) and a specific resource (free cash flow), and goes further by giving the exact formula (operating cash flow minus capital expenditure), which distinguishes it from neighbors like x402-price-to-cash-flow or x402-operating-cycle. It does not explicitly name a sibling alternative, so it falls short of a 5.

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 guidance on when to use this versus the many other finance/CFO calculators in the sibling list, nor any prerequisites or preconditions for calling it. The only situational text ('5 free trial calls per signed wallet') is a payment/trial note, not usage guidance.

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.