Skip to main content
Glama
Marketing Ops MCP

Marketing Ops MCP

design_experiment

Read-onlyIdempotent

Estimate sample size for a fixed-horizon two-proportion experiment using baseline rate, absolute MDE, alpha, and power to plan adequately powered tests.

Instructions

Estimate a fixed-horizon two-proportion experiment sample size.

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": {
      "payload": "<payload>"
    },
    "name": "design_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and closed-world. The description adds methodological context by specifying fixed-horizon and two-proportion estimation, but it does not disclose assumptions, output meaning, or limitations beyond those annotations.

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?

The description is a single front-loaded sentence with no wasted wording. It is as concise as possible for the stated purpose.

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?

For a statistical sample-size tool with nested parameters and no output schema, the description is too sparse. It omits input semantics, assumptions, and whether the result is per-arm or total sample size, so an agent cannot fully understand usage from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the required baseline_rate, absolute_mde, alpha, or power inputs. It only hints at the two-proportion method, leaving parameter meanings to the schema titles and defaults.

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: estimating sample size for a fixed-horizon two-proportion experiment. It is clear what the tool computes, though it does not explicitly differentiate itself from siblings such as analyze_experiment.

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 description provides no guidance on when to use this tool versus alternatives or when not to use it. It implies experiment planning usage through 'fixed-horizon two-proportion,' but does not state selection criteria or prerequisites.

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