razorpay-mcp

get_subscription_analytics

Analyze subscription performance by retrieving active counts, churn rate, MRR, and upcoming renewals within a specified date range.

Instructions

Analyze subscriptions — active count, churn rate, MRR, upcoming renewals

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_subscription_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`from`	Yes	Unix timestamp — start date
`to`	Yes	Unix timestamp — end date

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 25, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided, so the description should cover behavioral traits. It only lists output metrics without clarifying read-only nature, side effects, or performance, leaving ambiguity.

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?

Single sentence, no wasted words, clearly lists key metrics, and is front-loaded with purpose.

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?

For a simple 2-parameter tool with no output schema, the description sufficiently explains what metrics are returned, though could hint at return format.

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 coverage is 100% and both parameters are described adequately. The description adds no extra parameter context beyond the schema, meeting baseline.

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 the verb 'analyze' and resource 'subscriptions', and lists specific metrics (active count, churn rate, MRR, upcoming renewals), distinguishing it from siblings like get_subscription or list_subscriptions.

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 implies usage for aggregate analytics but does not explicitly state when to use this tool over alternatives like get_payment_analytics, nor provide prerequisites or exclusions.

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

Deploy Server