Skip to main content
Glama

Pause an experiment

pause_experiment
Idempotent

Pause a running test: nobody new enrolls, and users already in it keep their arm. resume_experiment picks it up again. Only works when the app allows MCP writes.

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": {
      "id": "<id>"
    },
    "name": "pause_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExperiment id, from list_experiments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a non-read-only, non-destructive, idempotent mutation, and the description earns its keep on top of that by spelling out exactly what state changes (enrollment halts, existing assignments preserved) and that the action is reversible via resume_experiment. It also discloses the MCP-writes permission requirement, a failure mode not captured by any annotation.

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, each doing distinct work: effect, reversibility/alternative, precondition. The most decision-relevant clause (no new enrollment) is front-loaded, and there is no filler.

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 one-parameter mutation with no output schema, the description covers the effect, the precondition, and the countervailing tool, which is enough to call it correctly. It does not indicate what the call returns or how to confirm the pause took effect, a minor gap given no output schema exists.

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 description says nothing about the single 'id' argument, but schema coverage is 100% and the schema itself explains the UUID format and points to list_experiments as the source. Baseline 3 is correct since the schema carries parameter meaning entirely.

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?

States a specific verb and resource ('Pause a running test') and immediately defines the observable effect: no new enrollments, existing participants retain their arm. That effect language distinguishes pause from stop_experiment and start_experiment without needing to name them.

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?

Names resume_experiment as the inverse operation and states a real precondition ('Only works when the app allows MCP writes'), which is a genuine gate an agent must check. It stops short of contrasting pause with stop_experiment, so the choice between those two is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources