Skip to main content
Glama

Resume an experiment

resume_experiment
Idempotent

Resume a paused test so new users enroll again. Refused when another test now holds its surface and placement. 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": "resume_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExperiment id, from list_experiments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

It adds real context beyond the annotations: conflict-refusal conditions and a permission gate on MCP writes. Idempotency and mutation semantics are already declared in annotations, and it does not say what happens to enrollment or data after resume, so a 4 isn't earned.

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?

Three short, front-loaded sentences with no filler; effect, refusals, and permission gate in that order. Slightly terse phrasing ("its surface and placement") that relies on domain knowledge keeps it from a 5.

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 annotations covering safety and idempotency, the description covers the key failure modes an agent needs. It could say what to do on refusal or whether the resume is reversible, but the essential call-shaping information is present.

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?

Single `id` parameter with 100% schema description coverage and a pattern/format already documented. The description adds no meaning about the id beyond what the schema says, so 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?

"Resume a paused test so new users enroll again" gives a specific verb and resource plus the effect of the action, which cleanly separates it from pause/stop/start siblings. It stops short of naming which sibling to use for a non-paused experiment, so not a 5.

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 description states two concrete preconditions for use: it is refused when another test holds the surface/placement, and it only works when the app permits MCP writes. It does not explicitly point to an alternative (e.g., start_experiment for a draft), leaving that inference to the agent.

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