Skip to main content
Glama
Stripe Testing Tools MCP Server

Stripe Testing Tools MCP Server

by hideokamoto

Advance Stripe Test Clock

advance_stripe_test_clock

Advance a Stripe test clock to a specified Unix timestamp to simulate time progression for subscription and billing testing scenarios.

Instructions

Advance a Stripe test clock to a specific time to simulate time progression

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

Input Schema

NameRequiredDescriptionDefault
frozen_timeYesUnix timestamp to advance the clock to
test_clock_idYesThe ID of the test clock to advance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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 description's only added value is the general notion of simulating time. It does not disclose that advancing is a mutating, effectively irreversible operation, that backwards movement is rejected, or that the clock transitions through a processing state.

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?

A single front-loaded sentence with zero filler; the verb, resource, and purpose land immediately.

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?

For a two-parameter tool with complete schema descriptions and no output schema, this is minimally adequate. However, the operationally important constraints (forward-only advancement, required clock state) are absent, which matters for correctly invoking a mutation 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 both parameters fully described including the Unix timestamp format for frozen_time. The description's phrase 'advance to a specific time' is consistent but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ('Advance a Stripe test clock') plus the intent ('simulate time progression to a specific time'). An agent can distinguish this from the sibling create/delete tools by name and description, but the description never explicitly contrasts it with them.

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?

No when-to-use guidance, no prerequisites, and no mention of the key constraint that Stripe test clocks can only move forward and require a ready status. The agent is left to infer usage entirely.

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