Skip to main content
Glama

BRAINIAC A/B Testing & Experimentation Statistics

Detect novelty or primacy effects in daily lift

experimentation_novelty-effect-detect
Read-onlyIdempotent

OLS trend test on daily lift with early-versus-late means, classifying the pattern as novelty, primacy or stable. Price $0.01 USDC. POST /api/v1/experimentation/novelty-effect-detect. 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": {
      "daily": "<daily>"
    },
    "name": "experimentation_novelty-effect-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
alphaNoalpha, number. Required.
dailyYesdaily, array. Required.
liftTypeNoliftType, string, one of relative, absolute. Optional.
earlyDaysNoearlyDays, integer, from 1 to 9007199254740991. Optional.

Output Schema

NameRequiredDescriptionDefault
tNot. Number.
pValueNopValue. Number.
patternNopattern. String.
slopeSeNoslopeSe. Number.
sourcesNosources. Array.
lateMeanNolateMean. Number.
liftTypeNoliftType. String.
earlyDaysNoearlyDays. Number.
earlyMeanNoearlyMean. Number.
limitationsNolimitations. Array.
slopePerDayNoslopePerDay. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: the $0.01 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms instead of running the analysis. It does not mention rate limits or failure modes, keeping it below 5.

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?

Three short sentences with the analytical purpose front-loaded, followed by payment mechanics. The raw endpoint path is marginally redundant with the tool's identity but still informative for billing/debugging. No filler or repetition.

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 annotations covering safety and an output schema covering return values, the description only needs to fill remaining gaps, and it does — the payment/auth flow is a non-obvious prerequisite an agent would otherwise stumble into. Only minor gaps remain, such as expectations about the `daily` series shape (ordering, minimum length).

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 all four parameters, though its text is largely boilerplate. The description adds only the concept of early-versus-late means, which loosely motivates `earlyDays` and `alpha` but gives no format, defaults, or boundary guidance beyond the schema. Baseline 3 applies.

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 a specific verb and resource — an OLS trend test on daily lift using early-versus-late means that classifies the pattern as novelty, primacy, or stable. That level of method specificity separates it from siblings like sequential-test or segment-lift without naming them. It stops short of explicit sibling differentiation, so 4 rather than 5.

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?

The output classification (novelty/primacy/stable) implies the use case — checking whether an effect decays or grows over the experiment window — but the description never states when to choose this over alternatives or what data conditions are required. Guidance is implied rather than stated.

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