paymongo-mcp

Get Checkout Session

get_checkout

Read-onlyIdempotent

Retrieve a PayMongo checkout session by its ID to inspect payment status and details.

Instructions

Retrieve a checkout session by its 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": {
      "checkout_session_id": "<checkout_session_id>"
    },
    "name": "get_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`checkout_session_id`	Yes	Checkout session ID (cs_...).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The description adds no behavioral context beyond what the annotations already provide. It simply restates the purpose and the lookup method, which is already evident from the schema. There is no mention of error handling, response details, rate limits, or other behavioral traits.

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 filler or redundant phrasing. It is appropriately front-loaded and every word contributes to conveying the tool's purpose.

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?

For a simple get-by-ID tool with one well-documented parameter and strong annotations, the description is sufficient. The operation is straightforward, and although it lacks usage context, the simplicity of the tool reduces the need for additional detail.

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%, so the schema already documents the sole parameter with a clear format hint ('cs_...'). The description's 'by its ID' adds no further semantic value, so the baseline of 3 is appropriate.

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 uses the specific verb 'Retrieve' and clearly identifies the resource as a 'checkout session' with lookup by ID. This distinguishes it from sibling tools like get_payment_intent or get_source, making the purpose unambiguous.

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 such as get_payment_intent or list_payments. It lacks any contextual cues about when this is the appropriate choice or what conditions warrant its use.

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