Skip to main content
Glama
Sign In
stripe-mcp-server

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Refunds

list_refunds
Read-only

Fetch a filtered list of refunds using payment intent, charge ID, or pagination parameters.

Instructions

List refunds with optional filtering.

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_refunds"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_intentNoFilter by PaymentIntent ID
chargeNoFilter by Charge ID
limitNoResults per page
starting_afterNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotation readOnlyHint=true already indicates this is a safe read operation. The description simply restates the listing behavior without adding extra context like pagination, rate limits, or what happens with no results. It is adequate but not enriched beyond the annotation.

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 extremely concise—only one phrase—which is efficient and front-loaded. However, it is so brief that it misses opportunities to add valuable information without becoming verbose. Still, it earns a 4 for no waste.

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?

Given the tool has four parameters and no output schema, the description lacks important details such as default behavior (e.g., ordering, maximum results), return format, or pagination cursor usage. It is incomplete for a comprehensive understanding, even with strong schema descriptions.

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 description coverage is 100%, so each parameter already has a clear description in the schema. The tool description adds no additional meaning or context beyond what is in the schema, 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.

Purpose4/5

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

The description clearly states 'List refunds with optional filtering,' which is a specific verb-resource combination. It distinguishes from siblings like create_refund and retrieve_refund, but could be more specific about the scope (e.g., all refunds) or default behavior.

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 when to use the tool (to list refunds with filters) but does not provide explicit guidance on when not to use it or mention alternative tools. Among many list siblings, no differentiation 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

Other Tools