Skip to main content
Glama

BRAINIAC A/B Testing & Experimentation Statistics

Compute sequential testing boundaries or an always-valid p-value

experimentation_sequential-test
Read-onlyIdempotent

Lan-DeMets group-sequential boundaries (O'Brien-Fleming or Pocock spending) for planned looks with a stop/continue decision, or an always-valid mSPRT p-value for continuous monitoring. Price $0.04 USDC. POST /api/v1/experimentation/sequential-test. An unpaid call returns the x402 payment terms and does not run.

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": {
      "mode": "<mode>"
    },
    "name": "experimentation_sequential-test"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesmode, string, one of group_sequential, msprt. Required.
tau2Notau2, number. Optional.
alphaNoalpha, number. Required.
estimateNoestimate, number. Optional.
spendingNospending, string, one of obrien_fleming, pocock. Required.obrien_fleming
varianceNovariance, number. Optional.
observedZNoobservedZ, array. Optional.
informationFractionsNoinformationFractions, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
decisionNodecision. Object.
spendingNospending. String.
boundariesNoboundaries. Array.
limitationsNolimitations. Array.
cumulativeAlphaNocumulativeAlpha. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real value beyond that by disclosing the $0.04 USDC cost and, importantly, that an unpaid call returns x402 payment terms without executing, which an agent must know. It does not disclose failure behavior for invalid inputs (e.g. informationFractions outside (0,1]) or whether results are deterministic across calls.

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?

Front-loaded with the analytical purpose, then cost, endpoint, and payment-gating caveat, so the important content comes first. The pricing, URL, and x402 sentences are operational boilerplate but each carries information the agent needs; three sentences for eight parameters is economical.

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?

With a full input schema, an output schema, and rich annotations, the description does not need to explain return values or safety. Given the tool's complexity (two analytically distinct modes, eight parameters), the remaining gap is the per-mode parameter assignment and required-vs-ignored fields, which is a meaningful but not fatal omission.

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%, so the baseline is 3 and the schema carries parameter documentation. The most valuable addition the description could make would be a mapping of which parameters belong to which mode (tau2/variance/estimate/observedZ for msprt versus informationFractions/spending for group_sequential), and that mapping is absent, so mode selection still requires inference from the schema.

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 two concrete statistical procedures (Lan-DeMets group-sequential boundaries with O'Brien-Fleming or Pocock spending, and an mSPRT always-valid p-value) and states the decision each produces. It distinguishes the two modes by analysis regime (planned looks vs continuous monitoring), though it never names a sibling such as the frequentist A/B test as the alternative for a fixed-horizon design.

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?

It gives clear internal routing: use group_sequential when there are pre-planned looks and you need a stop/continue decision, use msprt when monitoring continuously. That is genuine when-to-use guidance for the mode parameter, but there is no exclusion guidance against sibling tools and no statement of prerequisites (e.g. that informationFractions must be pre-specified before data collection).

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