Skip to main content
Glama
Sign In
RevClamp MCP Server

RevClamp MCP Server

Official
by revclamp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

revclamp_audit_revenue_leakage

Runs a deterministic 90-day audit of Stripe subscriptions, usage events, and disputes to identify B2B revenue leakage and assess Visa CE 3.0 readiness.

Instructions

Runs a deterministic 90-day B2B revenue leakage and Visa CE 3.0 readiness audit across caller-supplied Stripe subscriptions (2025-03-31.basil item-level periods), usage events, and disputes.

Input Schema

NameRequiredDescriptionDefault
demoNoSet true only to generate a labeled sample preview when customers/usageEvents are omitted.
disputesNoOptional array of Stripe dispute objects.
customersNoArray of Stripe customer objects with subscriptions ({ id, subscriptions: { data, has_more } }).
usageEventsNoArray of metered API/SaaS usage events ({ customer_id, event_name, occurred_at }).
costPerEventCentsNo
dunningGracePeriodDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.20.2
    • changedInput schema / properties / customers / description
      Previous value: -"Optional array of Stripe customer objects with subscriptions."New value: +"Array of Stripe customer objects with subscriptions ({ id, subscriptions: { data, has_more } })."
    • addedInput schema / properties / demo
      Added value: +{
+  "default": false,
+  "description": "Set true only to generate a labeled sample preview when customers/usageEvents are omitted.",
+  "type": "boolean"
+}
    • changedInput schema / properties / usageEvents / description
      Previous value: -"Optional array of metered API/SaaS usage events."New value: +"Array of metered API/SaaS usage events ({ customer_id, event_name, occurred_at })."
  2. Changed8 schema fields changedv1.20.1
    • addedInput schema / properties / costPerEventCents / default
      Added value: +142
    • removedInput schema / properties / costPerEventCents / description
      Removed value: -"Estimated marginal compute or API cost per leaked usage event in integer USD cents (valid range: 1 to 10000, default: 142 i.e. $1.42/event)."
    • changedInput schema / properties / costPerEventCents / maximum
      Previous value: -10000New value: +100000
    • changedInput schema / properties / customers / description
      Previous value: -"Optional array of up to 50 Stripe customer snapshots (each with id like 'cus_123', optional email, subscriptions array or list object, and subscriptionsHasMore: false). Omit to run against workspace telemetry or deterministic sandbox fixtures."New value: +"Optional array of Stripe customer objects with subscriptions."
    • changedInput schema / properties / disputes / description
      Previous value: -"Optional array of up to 50 Stripe dispute objects (each with id like 'du_123', customer, amount in cents, reason such as 'fraudulent', and status such as 'needs_response')."New value: +"Optional array of Stripe dispute objects."
    • addedInput schema / properties / dunningGracePeriodDays / default
      Added value: +3
    • removedInput schema / properties / dunningGracePeriodDays / description
      Removed value: -"Custom dunning grace window in integer days (valid range: 0 to 14, default: 3) allowed after latest_invoice_failed_at before flagging past_due subscriptions as unpaid ghost usage."
    • changedInput schema / properties / usageEvents / description
      Previous value: -"Optional array of up to 200 product/AI API usage telemetry events (each with stripe_customer_id or email, event_name, and occurredAtSec Unix timestamp in seconds)."New value: +"Optional array of metered API/SaaS usage events."
  3. First observedv1.20.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral-disclosure burden. It adds some useful context by saying the audit is deterministic, covers a 90-day window, and expects Stripe 2025-03-31.basil item-level subscription periods, but it does not state whether the tool is read-only, what permissions or auth are required, whether it mutates data, or what its output/error behavior is.

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 definition is a single front-loaded sentence that states the core action and scope without repetition or filler. It is appropriately sized for a tool with no annotations and no output schema, though the sentence is dense and packs technical details into one long clause.

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 complex audit tool with no annotations, no output schema, and only 67% parameter-description coverage, the description is incomplete. It identifies the audit scope and primary input categories but omits the return/report shape, safety profile, prerequisites, and semantics for costPerEventCents and dunningGracePeriodDays.

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 67%: 'demo', 'disputes', 'customers', and 'usageEvents' have schema descriptions, while 'costPerEventCents' and 'dunningGracePeriodDays' do not. The description mentions subscriptions, usage events, and disputes, aligning with three parameters, but it does not add meaning for the two undocumented economic parameters. A 3 is appropriate because the schema carries most of the semantic load and the description provides only partial mapping.

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 uses a specific verb ('Runs') and clearly names the resource: a 90-day B2B revenue leakage and Visa CE 3.0 readiness audit. It also scopes the tool to caller-supplied Stripe subscriptions, usage events, and disputes. It does not explicitly differentiate itself from related sibling tools such as revclamp_stage_stripe_dispute_ce3 or revclamp_lint_dispute_evidence, so it falls short of a 5.

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 gives no guidance on when to use this tool versus alternatives, nor does it state prerequisites or exclusions. The schema's 'demo' parameter hints at a sample-preview mode, but the description itself does not explain when to invoke the audit, when to avoid it, or how it relates to sibling audit/dispute tools.

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

Deploy Server

Other Tools