Skip to main content
Glama

Deferred Revenue Waterfall

bpj_deferred_revenue_waterfall
Read-onlyIdempotent

Roll opening deferred revenue and new advance billings forward after recognizing the delivered portion.

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": {
      "deferred": "<deferred>",
      "billed": "<billed>",
      "recognized": "<recognized>"
    },
    "name": "bpj_deferred_revenue_waterfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
billedYes
deferredYes
recognizedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, idempotentHint=true, and closed-world scope, so the safety profile is covered. The description adds the substantive behavioral point that recognition is applied before the roll-forward, which affects the computed result. It omits, however, whether the output is a single closing balance or a multi-column waterfall, and says nothing about rounding or currency/units, which matter for a monetary calculation.

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 the calculation order front-loaded and no filler. It is efficient but so terse that it leaves key questions unanswered, which is an under-specification issue rather than verbosity.

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 three-numeric-input calculation with no output schema, the description should at minimum indicate what is returned, since structured fields cannot convey that. It explains the computation flow but not the return value, units, or precision, leaving a real gap for a tool whose entire value is its computed 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 only bare titles ('Opening deferred revenue', 'New advance billings', 'Revenue recognized from advances') carry parameter meaning. The description restates all three concepts in plain language, giving a workable one-to-one mapping to deferred, billed, and recognized. It does not spell out the resulting relationship (closing = opening + new billings − recognized), so the agent still has to infer the arithmetic from the tool name.

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 gives a specific verb and domain object: roll opening deferred revenue and new advance billings forward after recognizing the delivered portion. An agent familiar with revenue accounting can tell this is a deferred-revenue roll-forward computation. It does not, however, distinguish itself from the sibling bpj_recurring_revenue_waterfall, so the agent cannot tell which waterfall applies to a given scenario.

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 pointer to the recurring-revenue sibling as an alternative, and no stated preconditions. The agent must infer applicability purely from the domain vocabulary in a single sentence.

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.