Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Create Stripe Test Clock

create_stripe_test_clock

Create a Stripe test clock with a specified frozen Unix timestamp to simulate and test time-based billing and subscription scenarios.

Instructions

Create a new Stripe test clock for time-based testing

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": {
      "frozen_time": "<frozen_time>"
    },
    "name": "create_stripe_test_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name for the test clock
frozen_timeYesUnix timestamp for the initial frozen time of the test clock

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-safety profile is covered. The description adds nothing beyond that: it does not say the clock is created in a sandboxed/test environment, whether it persists indefinitely, or what state a newly created clock starts in (which matters given frozen_time drives subsequent advance calls).

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?

A single front-loaded sentence with no filler, so nothing is wasted. It is arguably over-brief for a creation tool, but the structure itself is clean.

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

Completeness3/5

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

With only two fully-documented parameters and no output schema, the bar is low, and the description covers the core purpose. However, for a state-creating tool used in a test-clock workflow it omits the returned clock identity and the environment assumption, leaving an agent to infer how the new clock is referenced later.

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 both name and frozen_time are already documented in the schema. The description contributes no additional semantics such as the expected timestamp format, precision, or whether frozen_time can be in the past; baseline 3 applies.

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 gives a specific verb and resource ('Create a new Stripe test clock') plus the domain purpose ('for time-based testing'), which is enough to distinguish it from siblings like advance_stripe_test_clock or delete_stripe_test_customers by name alone. It does not explicitly name an alternative, but the create-vs-advance distinction is inferable from the sibling names and the verb.

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?

There is no explicit when-to-use or when-not-to-use guidance. 'For time-based testing' hints at the scenario but never states prerequisites, such as needing test-mode API keys, or when an agent should create a clock versus advance or reuse an existing one.

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