Skip to main content
Glama

Recurring Revenue Waterfall

bpj_recurring_revenue_waterfall
Read-onlyIdempotent

Reconcile opening MRR with new, expansion, contraction, churn and reactivation movements.

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": {
      "opening": "<opening>",
      "added": "<added>",
      "expansion": "<expansion>",
      "contraction": "<contraction>",
      "churn": "<churn>",
      "returned": "<returned>"
    },
    "name": "bpj_recurring_revenue_waterfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
addedYes
churnYes
openingYes
returnedYes
expansionYes
contractionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered by structured data. The description adds almost nothing beyond that: it does not say whether the tool verifies that the movements sum to closing MRR, whether it throws on imbalance, or how it treats signs. For a pure computation tool with no output schema, that is a real gap.

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 front-loaded sentence with no filler; every term maps to an input. It is efficient but so terse that useful detail was never included rather than trimmed.

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?

For a six-parameter, all-required computation with no output schema, the definition should describe the reconciliation identity and the return shape. Neither is present, so an agent cannot predict what it gets back or what constraints the inputs must satisfy.

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%, so the description must carry parameter meaning, and it only partially does. It names the movements in prose, but never states whether churn and contraction are supplied as positive magnitudes to be subtracted or as signed values, leaving ambiguity across all six required numeric parameters.

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 ("Reconcile") and resource (MRR movements), and enumerates the five movement types plus opening MRR that define the computation. It does not distinguish itself from the closely named sibling bpj_deferred_revenue_waterfall, so an agent cannot tell from the description alone which waterfall to use.

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 statement of when to use this tool versus alternatives, no prerequisites, and no acknowledgement of the deferred-revenue sibling. Usage is only implied by the domain vocabulary.

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.