Skip to main content
Glama

update_experiment

DestructiveIdempotent

Update experiment status (pause, resume, complete)

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>",
      "status": "<status>"
    },
    "name": "update_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExperiment ID
statusYesNew status
winnerNoWinning variant (for completing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=true, and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not warn that completing an experiment is irreversible, does not mention that a winner is needed to complete, and says nothing about permissions or side effects. For a destructive mutation this is a meaningful gap.

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?

One short sentence with the resource and the enumerated actions front-loaded; there is no filler or redundancy. The economy is appropriate, though it exposes how little is being said.

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

Completeness2/5

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

This is a destructive, three-parameter mutation with no output schema and no annotations explaining consequences, so the description carries real weight — yet it omits the winner parameter, the irreversibility of completing, and any notion of what happens on resume. The definition is not sufficient for an agent to call it confidently in edge cases.

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%, so all three parameters are documented in the schema itself, giving a baseline of 3. The description does add a light action-to-status mapping (pause→paused, resume→active, complete→completed), but it never mentions the 'winner' parameter or its link to the complete action, so it does not enrich the schema in any substantive way.

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 names a specific verb (Update) and resource (experiment status) and enumerates the three transitions, so the agent knows this is a status-change tool rather than the create/delete/get siblings. It does not explicitly differentiate itself from those siblings, and the verbs 'pause/resume/complete' do not literally match the enum values 'paused/active/completed'.

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?

The parenthetical implies when the tool applies (to pause, resume, or complete an experiment), but there is no explicit guidance on prerequisites, when not to use it, or how it relates to create_experiment/delete_experiment. An agent must infer everything about the workflow from the name alone.

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