Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

Official

revclamp_calculate_roi_and_plan_fit

Calculates monthly and annual B2B margin savings in USD cents by comparing flat 0% take-rate pricing with 25–30% contingency agencies, then recommends the optimal plan tier.

Instructions

Calculates monthly and annual B2B margin savings in integer USD cents comparing 0% take-rate flat pricing against 25%-30% chargeback contingency agencies and recommends the optimal tier.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revclamp_calculate_roi_and_plan_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthlyUsageEventsNo
monthlyGhostBleedUsdNo
monthlyWonDisputeUsdNo
contingencyTakeRatePercentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.20.1
    • addedInput schema / properties / contingencyTakeRatePercent / default
      Added value: +25
    • removedInput schema / properties / contingencyTakeRatePercent / description
      Removed value: -"Competitor chargeback agency contingency commission percentage (valid range: 1 to 50, default: 25 for 25% take-rate tools)."
    • addedInput schema / properties / monthlyGhostBleedUsd / default
      Added value: +600
    • removedInput schema / properties / monthlyGhostBleedUsd / description
      Removed value: -"Monthly unpaid AI/API or SaaS usage bleed stopped by RevClamp basil entitlement guards in USD (valid range: 0 to 10000000, default: 600)."
    • addedInput schema / properties / monthlyUsageEvents / default
      Added value: +250000
    • removedInput schema / properties / monthlyUsageEvents / description
      Removed value: -"Monthly verified usage events across your workspace (integer 0 to 50000000, default: 250000) used to recommend Starter (<=100k), Growth (<=1M), or Scale (<=5M)."
    • addedInput schema / properties / monthlyWonDisputeUsd / default
      Added value: +10000
    • removedInput schema / properties / monthlyWonDisputeUsd / description
      Removed value: -"Monthly won Stripe chargeback volume in USD (valid range: 0 to 10000000, default: 10000) subject to legacy agency take-rate fees."
  2. First observedv1.20.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavioural facts: the computation compares a 0% take-rate against a contingency take-rate, and results are expressed in integer USD cents. However it does not state that the operation is a side-effect-free simulation (no writes, no external calls), nor does it explain the model assumptions behind ghost bleed or won-dispute inputs, which matter for trusting the output.

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 dense sentence with no filler, and the core purpose is front-loaded in the opening verb. It packs comparison basis, units, and the recommendation into one clause chain, which is efficient though slightly breathless for a calculation with four opaque inputs.

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?

There is no output schema, and the description partially covers the return: monthly and annual savings plus a recommended tier. But for a four-parameter calculation with zero annotation and zero schema-description support, an agent still lacks the input semantics and the pricing model's assumptions needed to call it confidently with non-default values.

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 compensate and it largely does not: monthlyUsageEvents, monthlyGhostBleedUsd, and monthlyWonDisputeUsd are never mentioned, leaving the agent to guess units and role. The description also says contingency rates of '25%-30%' while the parameter allows 1–50, creating ambiguity about the meaningful range. The one genuine addition is the output unit (integer USD cents), which does not resolve the unclear input units (defaults such as 600 and 10000 look like dollars, not cents).

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 and resource: calculates monthly and annual B2B margin savings comparing flat 0% take-rate pricing against 25–30% contingency agencies, and recommends a tier. That is far more specific than any sibling (audit_revenue_leakage, evaluate_ghost_usage). The only soft spot is 'optimal tier', which is never defined and has no corresponding parameter, so an agent cannot tell what a tier is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the framing of the comparison — an agent can infer it is for pricing-model ROI evaluation rather than a sibling's audit/lint/validation job. There is no explicit when-to-use, no when-not-to-use, and no named alternative despite eight siblings that could plausibly be confused with a revenue-leakage calculation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.