Skip to main content
Glama

BRAINIAC A/B Testing & Experimentation Statistics

Adjust p-values for multiple testing

experimentation_multiple-testing-correct
Read-onlyIdempotent

Bonferroni, Holm and Benjamini-Hochberg adjusted p-values and reject decisions across metrics or arms, returned in input order. Price $0.01 USDC. POST /api/v1/experimentation/multiple-testing-correct. 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": {
      "pValues": "<pValues>"
    },
    "name": "experimentation_multiple-testing-correct"
  }
}

Input Schema

NameRequiredDescriptionDefault
alphaNoalpha, number. Required.
methodsNomethods, array. Required.
pValuesYespValues, array. Required.

Output Schema

NameRequiredDescriptionDefault
alphaNoalpha. Number.
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds important behavioral context beyond annotations: a $0.01 USDC price, an x402 payment gate, and the fact that an unpaid call returns payment terms without running the correction.

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 compact and front-loaded: it first states the statistical output and ordering behavior, then the price, endpoint, and unpaid-call behavior. Every sentence provides useful information with no filler.

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?

The tool is low-complexity with three well-documented parameters, rich annotations, and an output schema, so return-value details need not be repeated. The description covers output ordering, cost, endpoint, and payment behavior; the main remaining gap is explicit guidance on choosing this correction method over sibling tools.

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 schema already documents alpha, methods, pValues, and each pValue entry. The description reinforces method names and says results are returned in input order, but it does not add new meaning about parameter constraints or selection beyond 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 states a specific statistical operation: Bonferroni, Holm, and Benjamini-Hochberg adjusted p-values and reject decisions across metrics or arms. It is clearly distinguishable from most siblings by its multiple-testing correction focus, but it does not explicitly name when an alternative such as sequential testing is more appropriate.

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 'multiple testing' and 'across metrics or arms', which suggests the tool should be used when correcting many p-values. However, the description gives no explicit when-to-use or when-not-to-use guidance versus alternatives like experimentation_sequential-test.

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