razorpay-mcp

list_orders

Retrieve orders from your Razorpay account filtered by date range, status, receipt, or authorization state.

Instructions

List orders with optional filters

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>",
      "status": "<status>",
      "authorized": "<authorized>",
      "receipt": "<receipt>"
    },
    "name": "list_orders"
  }
}

Input Schema

Name	Required	Description
`from`	Yes	Unix timestamp — start date
`to`	Yes	Unix timestamp — end date
`count`	No	Number of records (max 100)
`skip`	No	Number of records to skip
`status`	Yes	Filter by order status
`authorized`	Yes	Filter by authorized state
`receipt`	Yes	Filter by receipt number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 25, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, auth requirements, rate limits, or response behavior. For a list tool, it should at least imply it is safe to call.

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?

The description is a single short sentence, efficient and front-loaded. However, it is almost too brief, lacking important details that could be added without becoming verbose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters (5 required), no output schema, and no annotations, the description is inadequate. It does not explain the return format, pagination, or filtering behavior beyond what the schema provides.

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?

Input schema has 100% coverage with good descriptions for each parameter. The description adds no additional meaning beyond the schema, so it meets the baseline expectation but does not enhance understanding.

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 'List orders with optional filters' clearly indicates the action (list) and resource (orders). It distinguishes from sibling 'get_order' which retrieves a single order, but does not explicitly differentiate from other list tools like list_payments.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no context about prerequisites, scenarios, or exclusions. Sibling tools like list_payments or list_subscriptions exist but no comparison is given.

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

Deploy Server