Skip to main content
Glama

Gross and Net Revenue Retention

bpj_gross_net_retention
Read-onlyIdempotent

Calculate gross and net dollar retention for the opening customer cohort, excluding new and reactivated accounts.

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>",
      "churn": "<churn>",
      "contraction": "<contraction>",
      "expansion": "<expansion>"
    },
    "name": "bpj_gross_net_retention"
  }
}

Input Schema

NameRequiredDescriptionDefault
churnYes
openingYes
expansionYes
contractionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real context by specifying cohort treatment of new and reactivated accounts, but says nothing about how gross vs net are computed or what units the result uses.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the scope qualifier follows the verb immediately.

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 pure four-input calculator with no output schema, the description should supply the gross and net formulas and the return shape (ratio, percentage, or currency). Both are absent, leaving the two headline outputs undefined.

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% — only titles ('Opening MRR', 'Churned MRR', 'Expansion MRR', 'Contraction MRR') and numeric bounds exist. The description does not add the formula or clarify edge cases (e.g., whether churn should include the accounts excluded as reactivated), which is exactly the gap the low coverage requires it to fill.

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?

Names a specific verb ('Calculate') and resource ('gross and net dollar retention') and narrows the scope to the opening customer cohort while excluding new and reactivated accounts. That scope clause is what distinguishes it from a naive retention calculation, though no sibling tool is named for contrast.

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?

The description states a scope constraint but gives no when-to-use guidance, no prerequisites, and no pointer to alternatives such as bpj_retention_offer_lift_value. An agent must infer context from the name alone.

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.