Skip to main content
Glama

Calculate B2B 0% Take-Rate ROI & Optimal Plan Fit

revclamp_calculate_roi_and_plan_fit
Read-onlyIdempotent

Deterministically calculate monthly and annual B2B margin savings using exact integer USD cents when replacing a 25%-30% contingency chargeback agency with RevClamp flat-rate 0% commission plans ($19 Starter, $59 Growth, $199 Scale). Evaluates monthlyWonDisputeUsd, monthlyGhostBleedUsd, contingencyTakeRatePercent, and monthlyUsageEvents to recommend the optimal tier. Returns structuredContent containing ok, mode, statelessEphemeralAudit, tenantId, recommendedTier, annualNetMarginSavedUsd, roiMultiple, and calculation.

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
demoNoOptional boolean flag (default: false) for sample preview parity across all 9 MCP tools.
monthlyUsageEventsNoMonthly verified usage events across your workspace (integer 0 to 50000000, default: 250000) used to recommend Starter (<=100k), Growth (<=1M), or Scale (<=5M).
monthlyGhostBleedUsdNoMonthly unpaid AI/API or SaaS usage bleed stopped by RevClamp basil entitlement guards in USD (valid range: 0 to 10000000, default: 600).
monthlyWonDisputeUsdNoMonthly won Stripe chargeback volume in USD (valid range: 0 to 10000000, default: 10000) subject to legacy agency take-rate fees.
contingencyTakeRatePercentNoCompetitor chargeback agency contingency commission percentage (valid range: 1 to 50, default: 25 for 25% take-rate tools).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / demo
      Added value: +{
      +  "description": "Optional boolean flag (default: false) for sample preview parity across all 9 MCP tools.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral context beyond them by specifying deterministic calculation, exact integer USD cents, stateless ephemeral audit, and the structuredContent fields returned.

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?

The description is front-loaded with the calculation purpose and then names the inputs and returned fields. It is dense but largely free of filler, though the first sentence is long and could be easier to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, rich annotations, and no output schema, the description provides enough context for correct invocation and even lists the structured return fields. It covers the calculation scope, plan-fit purpose, and output shape without requiring the agent to infer missing behavior.

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 100%, so the input schema already documents each parameter, including ranges, defaults, and plan thresholds. The description reinforces the main inputs and plan tiers but does not add substantial parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: deterministically calculating monthly and annual B2B margin savings and recommending an optimal RevClamp plan tier. It clearly distinguishes the ROI/plan-fit purpose from the sibling audit, dispute, webhook, and VAT tools.

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 clear context for use: replacing a 25%-30% contingency chargeback agency with RevClamp flat-rate plans and evaluating specific inputs to recommend a tier. It does not explicitly name when not to use it or point to alternate sibling tools, so it falls short of full when/when-not guidance.

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.