Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

revclamp_evaluate_ghost_usage

Checks if a metered API/SaaS usage event belongs to an entitled customer or is post-cancellation/post-grace ghost usage under Stripe 2025-03-31.basil.

Instructions

Evaluates whether a metered API/SaaS usage event belongs to an entitled customer or represents post-cancellation / post-grace ghost usage under Stripe 2025-03-31.basil.

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_evaluate_ghost_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNo
timestampNoOptional alias for occurredAt (ISO-8601 string, Unix epoch seconds, or Unix epoch milliseconds).
customerIdNoOptional Stripe customer identifier to evaluate (e.g. 'cus_9s6XKzkNRiz8i3', max 64 chars).
occurredAtNoOptional usage event timestamp as ISO-8601 string, Unix epoch seconds, or Unix epoch milliseconds.
usageEventNoOptional metered usage event with customer_id, event_name, occurred_at (or occurred_at_sec).
occurred_atNoOptional snake_case alias for occurredAt (ISO-8601 string, Unix epoch seconds, or Unix epoch milliseconds).
occurredAtSecNoOptional alias for usageTimestampSec (Unix epoch seconds, Unix epoch milliseconds, or ISO-8601 string).
subscriptionsNoStripe subscriptions list envelope ({ data: [...], has_more: false }) or raw array of subscription objects.
currentPeriodEndNoOptional camelCase alias for current_period_end (Unix epoch seconds, epoch milliseconds, or ISO-8601 string).
usageTimestampSecNoOptional usage event timestamp as Unix epoch seconds, Unix epoch milliseconds, or ISO-8601 string.
current_period_endNoOptional flat subscription current_period_end (Unix epoch seconds, epoch milliseconds, or ISO-8601 string).
subscriptionStatusNoOptional flat Stripe subscription status shorthand ('active', 'trialing', 'past_due', 'canceled', 'unpaid', 'incomplete', 'incomplete_expired', 'paused') when subscriptions is omitted.
currentPeriodEndSecNoOptional flat subscription current_period_end in Unix epoch integer seconds.
subscription_statusNoOptional snake_case alias for subscriptionStatus.
subscriptionsHasMoreNoPagination completeness flag (must be false when passing a raw subscriptions array).
dunningGracePeriodDaysNo
latestInvoiceFailedAtSecNoOptional flat latest_invoice_failed_at timestamp in Unix epoch integer seconds for past_due grace evaluation.
latest_invoice_failed_atNoOptional flat latest_invoice_failed_at timestamp (Unix epoch seconds, epoch milliseconds, or ISO-8601 string).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.20.33
    • addedInput schema / properties / occurredAt / minimum
      Added value: +1
    • addedInput schema / properties / occurredAt / type
      Added value: +[
      +  "integer",
      +  "string"
      +]
    • changedInput schema / properties / occurredAtSec / description
      Previous value: -"Optional alias for usageTimestampSec."New value: +"Optional alias for usageTimestampSec (Unix epoch seconds, Unix epoch milliseconds, or ISO-8601 string)."
    • changedInput schema / properties / occurredAtSec / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
    • addedInput schema / properties / occurred_at / minimum
      Added value: +1
    • addedInput schema / properties / occurred_at / type
      Added value: +[
      +  "integer",
      +  "string"
      +]
    • addedInput schema / properties / timestamp / minimum
      Added value: +1
    • addedInput schema / properties / timestamp / type
      Added value: +[
      +  "integer",
      +  "string"
      +]
    • changedInput schema / properties / usageTimestampSec / description
      Previous value: -"Optional Unix epoch timestamp in integer seconds when the usage event occurred."New value: +"Optional usage event timestamp as Unix epoch seconds, Unix epoch milliseconds, or ISO-8601 string."
    • changedInput schema / properties / usageTimestampSec / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Addedv1.20.29
  3. Removedv1.0.1
  4. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the evaluation is read-only, whether it performs any mutation or side effects, what permissions or Stripe API access are required, or what the response contains; it only names the entitlement/ghost-usage decision being made.

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 with no wasted wording. It is concise and readable, though its brevity is also the source of missing guidance for a complex 18-parameter tool.

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 an 18-parameter tool with nested objects, aliases, no required parameters, no annotations, and no output schema, the description is substantially incomplete. It does not explain the decision criteria for ghost usage, how subscriptions and grace/dunning fields interact, or what the evaluation returns.

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 high at 89%, so the schema already documents most parameters, including many aliases and timestamp formats. The description adds no parameter-level meaning beyond that, which meets the baseline of 3, but it does not explain how the 18 optional flat, nested, and alias fields should be combined.

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 states a specific verb and resource: evaluates whether a metered API/SaaS usage event belongs to an entitled customer or is post-cancellation/post-grace ghost usage. It is clear and distinguishable from siblings like revenue-leakage auditing or dispute-evidence linting, though it does not explicitly name an alternative.

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?

The intended use is implied by the evaluation question, but there is no explicit when-to-use guidance, no exclusions, and no stated alternatives or prerequisites. An agent can infer the scenario but must decide on its own when this tool is preferable to the revenue-leakage or reconciliation siblings.

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