Skip to main content
Glama

BRAINIAC A/B Testing & Experimentation Statistics

Measure A/B lift per segment with FDR control

experimentation_segment-lift
Read-onlyIdempotent

Per-segment conversion lift with Benjamini-Hochberg adjusted p-values, a Cochran Q heterogeneity test and suppression of small segments. Price $0.02 USDC. POST /api/v1/experimentation/segment-lift. 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": {
      "segments": "<segments>"
    },
    "name": "experimentation_segment-lift"
  }
}

Input Schema

NameRequiredDescriptionDefault
alphaNoalpha, number. Required.
segmentsYessegments, array. Required.
minUsersPerArmNominUsersPerArm, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
segmentsNosegments. Array.
suppressedNosuppressed. Array.
limitationsNolimitations. Array.
heterogeneityNoheterogeneity. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the price ($0.02 USDC), the x402 payment flow, and the fact that an unpaid call returns payment terms without running the analysis. It also names the statistical adjustments applied, which materially affects how results should be interpreted.

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?

Three short sentences: method first, then cost, then the unpaid-call behavior. No filler, and the most decision-relevant information (what it computes and what it costs) is front-loaded.

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 an output schema present and full schema coverage, the description need not explain return values or parameters. The remaining gap is the absence of any routing guidance to sibling statistical tests, which matters given the crowded experimentation namespace.

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% and every parameter is documented in the schema, so the baseline of 3 applies. The description only hints at minUsersPerArm through 'suppression of small segments' and adds no format or interpretation detail for alpha, segments, control, or treatment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific statistical operation — per-segment conversion lift with Benjamini-Hochberg adjusted p-values, a Cochran Q heterogeneity test, and small-segment suppression — which is concrete enough to separate it from siblings like multiple-testing-correct or ab-test-frequentist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the described method (segment-level lift with FDR control), but the definition never states when to pick this over experimentation_multiple-testing-correct or experimentation_ab-test-frequentist, nor any exclusion conditions. The payment-related guidance is the only explicit conditional behavior provided.

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