Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-days-sales-outstanding

Days Sales Outstanding: Computes days sales outstanding as 365 divided by revenue over average receivables 🆓 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-days-sales-outstanding"
  }
}

Input Schema

NameRequiredDescriptionDefault
revenueNo
averageReceivablesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / averageReceivables / description
      Removed value: -"AverageReceivables to process"
    • removedInput schema / properties / revenue / description
      Removed value: -"Revenue to process"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It exposes the underlying formula, which is useful, but it says nothing about output format, rounding/precision, whether values are annualized consistently, or error behavior when receivables is zero. The formula phrasing ('365 divided by revenue over average receivables') is also ambiguous about operator order.

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

Conciseness3/5

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

The definition is short and front-loads the metric name and formula, which is good. However, the trailing emoji free-trial advertisement is promotional content that does not help an agent invoke the tool and dilutes the otherwise efficient one-sentence structure.

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 simple 2-parameter, no-annotation, no-output-schema computation tool, the description gives enough to understand the intent. It nevertheless leaves gaps on input string format, output shape, and the precise formula ordering that an agent needs to call it correctly and interpret the result.

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 0%, so the description must compensate. It names both parameters implicitly through the formula (revenue, average receivables), which is more than the schema offers, but it does not specify the expected string format (decimal? percentage? thousands separator? currency?) or required period alignment that would make the strings usable.

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 the exact metric ('days sales outstanding'), so the resource is unambiguous. It doesn't differentiate itself from closely related siblings such as x402-receivables-turnover or x402-operating-cycle, but the purpose itself is clear.

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 tool versus alternatives like x402-receivables-turnover, no prerequisites (e.g. that revenue and receivables must be for the same period), and no exclusions. The only extra sentence is promotional pricing ('5 free trial calls per signed wallet'), which is 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.