Skip to main content
Glama
Sign In
razorpay-mcp

razorpay-mcp

by indiamcp
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

list_customers

Retrieve a list of customers from your Razorpay account with optional filters for count and pagination.

Instructions

List customers with optional filters

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

Input Schema

NameRequiredDescriptionDefault
countNoNumber of records (max 100)
skipNoNumber of records to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only says 'list customers' and 'with optional filters', but does not mention read-only nature, authentication, rate limits, ordering, or any side effects. This is insufficient for a tool with no annotation support.

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

Conciseness3/5

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

The description is very concise with a single sentence, but it is under-specified and lacks important details. Conciseness should not come at the cost of informativeness.

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?

The tool is simple with two pagination parameters and no output schema, but the description fails to mention returning format, ordering, or pagination behavior. Given the minimal annotations, the description should cover more behavioral aspects.

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 schema has 100% description coverage for parameters, so the baseline is 3. The description adds 'optional filters' which is not reflected in the schema, potentially causing confusion. It does not add meaningful semantic details beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List customers with optional filters', which clearly indicates the action of listing customers. However, the mention of 'optional filters' is misleading because the schema only provides pagination parameters (count, skip) and no actual filtering capabilities. This reduces clarity.

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 is given on when to use this tool versus siblings like get_customer (single customer) or other list_* tools. The description lacks context on when to choose this tool over alternatives.

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