Skip to main content
Glama

Cash Conversion Cycle

bpj_cash_conversion_cycle
Read-onlyIdempotent

Combine receivable, inventory and payable days into an operating cycle and a cash conversion cycle.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dso": "<dso>",
      "dio": "<dio>",
      "dpo": "<dpo>"
    },
    "name": "bpj_cash_conversion_cycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
dioYes
dpoYes
dsoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so the safety profile is fully covered. The description adds the useful fact that two results (operating cycle and cash conversion cycle) are returned, which matters because there is no output schema. It stops short of the actual arithmetic (OC = DSO + DIO, CCC = DSO + DIO − DPO), which is the defining behavior of a pure calculator.

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?

A single well-formed sentence with no filler, and the input-to-output relationship is front-loaded. Minor loss: "operating cycle" is introduced without definition, so the sentence is terse at the cost of a little precision.

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

Completeness2/5

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

This is a three-parameter arithmetic tool with no output schema and no parameter descriptions, so the description is the only place formulas, output shape, and interpretation could live — and none of that is present. An agent can guess what to pass but cannot confirm what it will get back or how to interpret a positive versus negative CCC.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — the schema supplies only titles ("Days sales outstanding", etc.) and numeric bounds. The description loosely maps "receivable, inventory and payable days" onto dso/dio/dpo, but adds no clarification of period basis, unit consistency, or how the values relate to the two reported cycles.

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 names a specific verb ("combine") and the exact inputs (receivable, inventory, payable days) and states the two derived measures produced. It does not, however, distinguish this from cash-oriented siblings such as bpj_cash_runway or bpj_free_cash_after_capex, so an agent must infer boundaries from the name 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 explicit when-to-use or when-not-to-use guidance, no mention of the alternative cash/efficiency metrics among siblings, and no stated preconditions (e.g., values must be in days, same period basis). Usage must be inferred entirely from the parameter names.

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.