Skip to main content
Glama

create_experiment

Idempotent

Create an A/B experiment

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": {
      "project": "<project>",
      "name": "<name>",
      "variants": "<variants>",
      "goal_event": "<goal_event>"
    },
    "name": "create_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExperiment name
projectYesProject name
weightsNoVariant weights, e.g. [50, 50]
variantsYesVariant keys, e.g. ['control', 'new_cta']
goal_eventYesGoal event name to measure conversions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no note on what happens when an experiment with the same name exists, no mention that project and goal_event must already exist, and no disclosure of validation failures. For a mutation tool that is largely what the annotations leave open.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At four words the description is front-loaded and free of waste, but it is under-specified rather than concise. Brevity here is achieved by omitting information rather than by compressing it.

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?

The tool requires four of five parameters, creates a stateful resource, and has no output schema, so the description should say at minimum that an existing project and goal event are needed and what is returned. None of that is present, leaving the agent reliant on the schema alone.

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%, with each of the five parameters documented including examples for variants and weights. The description contributes no additional meaning, so the baseline of 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ("Create an A/B experiment"), which is enough to separate it from the get/update/delete/list experiment siblings by verb alone. It stops short of explicitly contrasting itself with those siblings, so it sits just below the top band.

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 guidance on when to use this versus alternatives such as create_project or update_experiment, and no mention of prerequisites like an existing project or pre-defined goal event. The agent must infer all usage context from the name.

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