razorpay-mcp

get_subscription

Retrieve detailed information about a subscription by providing its unique ID. Access status, plan, and billing data.

Instructions

Fetch details of a specific subscription

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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "get_subscription"
  }
}

Input Schema

Name	Required	Description	Default
`subscription_id`	Yes	Subscription ID, e.g. sub_xxxxx

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 25, 2026

TDQS

A3.7/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 disclose behavioral traits. It only states 'Fetch details'—a read operation—but does not mention any side effects, permissions, return structure, or rate limits. Minimal transparency beyond the basic action.

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?

The description is a single, efficient sentence (6 words) with no filler. It earns its place without excess.

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?

Given the tool has only one parameter, no output schema, and no annotations, the description is adequate for a simple retrieval but lacks details on return format or potential errors. Could be more informative.

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?

The input schema has 100% coverage for the single parameter (description includes 'Subscription ID, e.g. sub_xxxxx'). The tool description adds no additional parameter meaning, so baseline score of 3 is appropriate.

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 'Fetch details of a specific subscription' uses a specific verb ('Fetch') and resource ('a specific subscription'), clearly distinguishing it from sibling tools like list_subscriptions (batch) and get_subscription_analytics (aggregate). No tautology or ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies usage when a subscription ID is available, it does not explicitly state when to use this tool versus alternatives like list_subscriptions. The context is clear but lacks exclusions or direct comparisons.

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

Deploy Server