Skip to main content
Glama

get_working_capital_benchmark

Read-only

Use when benchmarking working capital efficiency or preparing a CFO cash management brief. Working capital benchmarks — DSO, DPO, DIO, and cash conversion cycle (CCC) by industry and company size. Source: Hackett Group annual survey and BLS composite. CFO and treasury benchmark for lender covenant prep and cash flow optimization. $0.02 USDC per call.

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": {
      "industry": "<industry>"
    },
    "name": "get_working_capital_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYes
company_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint true, destructiveHint false) and scope (openWorldHint true). Beyond that the description adds genuinely useful operational facts the annotations cannot: the data provenance (Hackett Group annual survey plus BLS composite) and the per-call price of $0.02 USDC, which matters for cost-aware agents. It still says nothing about freshness, sample coverage, or what a response entry 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 a 'Use when...' clause, then the data scope, then provenance, then price — a sensible priority order. The 'CFO and treasury benchmark for lender covenant prep and cash flow optimization' clause partially restates the opening use-case sentence and could be trimmed.

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?

With no output schema, the description does the work of naming the returned metrics and their segmentation, plus the source and cost. Only minor gaps remain: no indication of response shape beyond the metric list and no note on how the optional company_size affects results.

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

Parameters4/5

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

Both parameters are enum-constrained in the schema, so allowed values are self-documenting; the description adds the meaning that the benchmark is segmented 'by industry and company size', tying the parameters to the output structure. It does not say whether company_size is optional in practice or what default/aggregate is returned if omitted.

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 resource (working capital benchmarks) and enumerates the metrics returned (DSO, DPO, DIO, CCC) with the segmentation dimensions (industry, company size). It is clearly distinguishable from siblings by domain, though it never explicitly contrasts with a named alternative benchmark tool.

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?

It gives concrete use cases: benchmarking working capital efficiency, preparing a CFO cash management brief, lender covenant prep, and cash flow optimization. It stops short of saying when NOT to use it or pointing to a related sibling, but the intended context is unambiguous.

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.

Resources