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

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Retrieve Dispute

retrieve_dispute
Read-only

Retrieve complete details of a Stripe dispute using its dispute ID, including evidence and resolution status.

Instructions

Retrieve a dispute by ID with full details.

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": {
      "dispute_id": "<dispute_id>"
    },
    "name": "retrieve_dispute"
  }
}

Input Schema

NameRequiredDescriptionDefault
dispute_idYesDispute ID (dp_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds 'with full details', but does not disclose additional behavioral traits like idempotency or rate limits. With annotations covering safety, a score of 3 is appropriate.

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, front-loaded sentence with no unnecessary words. Every word earns its place.

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?

Given the tool's simplicity (one parameter, no output schema, clear annotations), the description is mostly complete. It could be improved by hinting at what 'full details' include, but it's sufficient for a basic retrieval tool.

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% with a single parameter that has a description and pattern. The description's 'by ID' adds no new meaning beyond what the schema provides, so baseline 3 is correct.

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 the verb 'retrieve' and the resource 'dispute by ID', and implies it returns full details. It distinguishes from the sibling 'list_disputes' by specifying a single dispute retrieval, though not explicitly.

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 retrieving a specific dispute, but does not provide explicit guidance on when to use it vs alternatives or any exclusions. For a simple retrieval tool, usage is implied.

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