Skip to main content
Glama

Saas performance

saas_performance
Read-onlyIdempotent

Stripe billing, RevenueCat revenue metrics and PostHog product performance for SaaS: active subscriptions, trials, normalized MRR, ARR, collected payments, refunds and daily product events. Also returns customer and subscription counts by actual billing cadence when customer-level subscription data is available: how many customers pay annually or monthly. RevenueCat ARR is normalized MRR multiplied by 12. Each source and currency stays explicit, and no attribution is inferred without an identity join.

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": {
      "input": "<input>"
    },
    "name": "saas_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: RevenueCat ARR is defined as normalized MRR × 12, each source and currency stays explicitly labeled, no attribution is inferred without an identity join, and cadence breakdowns only appear when customer-level subscription data exists. Lacks any note on latency, limits, or result shape, so not a 5.

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?

Front-loaded with sources and metric families, then caveats, which is the right ordering for an agent scanning for relevance. The cadence sentence is slightly redundant ('counts by actual billing cadence ... how many customers pay annually or monthly'), but overall there is little wasted text.

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 no output schema, the description carries the return-value burden and does so by enumerating metric families, the ARR normalization rule, currency/source labeling, and the identity-join caveat for attribution. For a read-only, closed-world, time-ranged metrics tool this covers what an agent needs to call and interpret it; only sibling routing is missing, which the usage dimension already penalizes.

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 75%, so the schema already explains the date range, accountIds narrowing, userStatement, and idempotencyKey. The description adds no additional meaning about any of the four parameters — notably it never explains the date-range semantics or the account-scoping behavior itself.

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 names concrete upstream sources (Stripe billing, RevenueCat revenue metrics, PostHog product performance) and enumerates the metric families returned (active subscriptions, trials, normalized MRR, ARR, collected payments, refunds, daily events), which is far more specific than the vague tool name 'saas_performance'. It does not explicitly contrast itself with the many performance/revenue siblings (metrics_daily, performance_period, store_revenue), keeping it 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?

There is no guidance on when to choose this tool over sibling tools such as metrics_daily, performance_period, store_revenue, or business_review. The only conditional wording ('when customer-level subscription data is available') describes a data-availability caveat rather than an invocation rule.

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.