Skip to main content
Glama

Revenue summary

revenue_summary
Read-only

Retrieves monthly recurring revenue from active customers and splits it by plan, enabling clear answers to questions about revenue composition.

Instructions

Monthly recurring revenue (MRR) from active customers, split by plan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral content by scoping to active customers and declaring a per-plan grouping, but it omits the time window the 'monthly' figure is anchored to, currency, and whether discounts or churn are factored in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the metric acronym is expanded and the scope qualifiers arrive in one pass. Nothing is wasted and nothing important is buried.

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?

With no output schema and no parameters, the description carries most of the explanatory burden itself. It defines the metric but not the return structure of the per-plan split, the period boundary, or the currency, which leaves an agent guessing at what it will actually receive.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to add and the baseline of 4 applies. The description's mention of 'active' and 'by plan' correctly signals that these are fixed, non-configurable dimensions rather than inputs.

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 a concrete metric (monthly recurring revenue), its population (active customers), and its breakdown (by plan). That is specific enough to distinguish it from the sibling tools find_customer and signups_this_week, though it never explicitly states the contrast.

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?

Usage is only implied: an agent can infer this is the tool for revenue reporting, but there is no statement of when to call it versus when not to, nor any pointer to related metrics. Since the siblings are unrelated lookups, the missing routing guidance is a minor rather than crippling gap.

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