Skip to main content
Glama

Lovie Company Formation

Get Recurring Revenue

stripe_get_recurring_revenue
Read-only

The company's monthly recurring revenue (MRR) from its connected Stripe accounts, per currency, with the number of active subscriptions: each subscription item's price times its quantity brought to a month by its billing interval, after the subscription's coupon; trials are left out. connected is false when no Stripe account is connected. Quote the figure as returned. Read-only.

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": "stripe_get_recurring_revenue"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdNo

Output Schema

NameRequiredDescriptionDefault
asOfNo
revenueNo
connectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint, and 'Read-only' merely repeats that. Beyond them, the description discloses the full calculation methodology (price×quantity prorated by billing interval, coupon applied first, trials excluded) and the empty-state signal 'connected is false', which is genuinely useful behavioral context. The instruction to quote the figure as returned also constrains how the agent should present 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?

One dense but carefully ordered sentence: metric, grouping, count, then formula detail, then edge case, then display rule. Nothing is filler, though the embedded formula clause makes it slightly hard to scan on first read.

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?

An output schema exists and annotations cover safety, so the description's job is mainly methodology and scoping, which it does well. It is still incomplete on two points an agent needs: whether companyId is optional/defaulting to the caller's company, and what the tool is not for relative to accounting revenue reports.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one optional parameter (companyId) at 0% schema coverage, and the description supplies the meaning it lacks: 'The company's ... MRR from its connected Stripe accounts' makes clear the call is scoped to a single company, and the singular company framing signals the default when no companyId is passed.

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?

States a specific metric (monthly recurring revenue from connected Stripe accounts), its grouping (per currency), its accompanying count (active subscriptions), and the exact computation formula. An agent can distinguish this from siblings like get_income_by_category or updates_get_metrics_snapshot without opening any schema.

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 description defines the applicable scope implicitly: only connected Stripe accounts, trials excluded, and 'connected is false' when nothing is linked. However, it never routes the agent among alternatives (e.g., accounting revenue reports or income-by-category tools) or says what to do when connected is false.

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.