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

stripe-mcp-server

by udaykapur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Retrieve Charge

retrieve_charge
Read-only

Retrieve a charge by its unique ID to access full payment details, including status and amount.

Instructions

Retrieve a charge by ID.

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": {
      "charge_id": "<charge_id>"
    },
    "name": "retrieve_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
charge_idYesCharge ID (ch_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The description matches the readOnlyHint annotation, indicating a read-only operation. However, it does not add information beyond the annotation, such as behavior on missing ID or response format.

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, clear sentence with no unnecessary words. It is appropriately concise for a simple tool.

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

Completeness5/5

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

Given the tool's simplicity (1 required parameter, no output schema, read-only annotation), the description is complete and sufficient for an agent to understand its purpose and usage.

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 fully describes the parameter with pattern and description (100% coverage). The description adds no additional semantic meaning beyond what the schema provides.

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 'Retrieve a charge by ID' uses a specific verb (Retrieve) and resource (charge), and clearly distinguishes from sibling tools like 'list_charges' which retrieves multiple charges.

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 the tool is for retrieving a single charge by ID, but lacks explicit guidance on when to use it over alternatives (e.g., when to use list_charges or other retrieve tools). No exclusions or context provided.

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