Skip to main content
Glama
Sign In
Retain MCP Server

Retain MCP Server

Official
by retain-so
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get churn metrics

get_churn_metrics

Calculate current period churn metrics including churn rate, MRR churned, and net revenue retention to assess customer retention performance.

Instructions

Consolidated metrics for the current period: churn rate, MRR churned, new/expansion/contraction MRR and net revenue retention.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It implies a read operation but does not define 'current period,' data freshness, permission requirements, or anything about mutability. The description is too terse for a tool with zero annotations.

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 sentence that packs all relevant information—no wasted words, front-loaded with purpose, and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 adequately lists the metrics returned. However, it lacks details like numerical format (e.g., percentages vs. absolute) or time range definition (e.g., month-to-date). Still, for a simple metrics endpoint, it is largely complete.

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?

No parameters exist, and schema coverage is 100%. The description adds value by enumerating the returned metrics (churn rate, MRR churned, net revenue retention), which goes beyond the empty schema. Baseline for 0 params is 4, and this meets it.

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?

The description clearly states it provides 'consolidated metrics for the current period' and lists specific metrics (churn rate, MRR churned, net revenue retention), making the purpose distinct from siblings like get_mrr_at_risk or get_at_risk_customers.

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?

No guidance on when to use this tool versus alternatives. The description does not mention scenarios where other tools (e.g., get_mrr_at_risk) would be more appropriate, nor does it specify prerequisites or context.

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