Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Start Card Setup

startCardSetup
Destructive

Creates a SetupIntent for saving a card with Stripe's inline payment element and returns a client secret the browser exchanges to store the card for the caller's customer.

Instructions

Create a SetupIntent for saving a card with the inline payment element. Returns a clientSecret that Stripe's payment element exchanges for a saved card in the browser. The secret alone cannot charge anything or read existing cards, and it is scoped to the caller's own Stripe customer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=true, so the safety profile is partly covered. The description still adds substantive context beyond that: it discloses the return value shape (clientSecret), and crucially bounds the secret's power ('cannot charge anything or read existing cards') and its scope ('caller's own Stripe customer'). It stops short of covering idempotency, secret expiry, or how long the SetupIntent persists, and it does not explain why a card-save operation is flagged destructive, which is the one point an agent might find confusing.

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?

Three short sentences with zero padding. The action is front-loaded, followed by the return value, then the security boundary, which is exactly the order an agent needs.

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?

For a zero-parameter, no-output-schema tool, the description covers everything required: what is created, what comes back, how it is used, and what the returned secret cannot do. Nothing an agent needs to call or interpret this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics burden and the baseline is 4. The description correctly implies that no caller-supplied arguments are needed, since the customer context is implicit in the caller's identity.

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 names a specific verb and resource ('Create a SetupIntent') and states the exact use case ('saving a card with the inline payment element'). This is clearly distinct from every sibling tool in the list, none of which touch card/payment objects, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: this is the entry point when the inline payment element needs a secret to save a card in the browser, and the flow (clientSecret handed to the element, exchanged in the browser) explains how it is consumed. No explicit 'when not to use' or alternative tool is named, but there is no card-setup sibling to route away from, so the omission is minor.

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