Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Generate a designed experiment

statistics_doe-design-generate
Read-onlyIdempotent

Full and fractional factorial (with defining relation, resolution and alias structure), Plackett-Burman and central composite designs in standard order, optionally randomised with a seeded xorshift128+ shuffle that is reproducible across languages. Price $0.03 USDC. POST /api/v1/statistics/doe-design-generate. 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": {
      "type": "<type>",
      "factors": "<factors>"
    },
    "name": "statistics_doe-design-generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoseed, integer, from -9007199254740991 to 9007199254740991. Required.
typeYestype, string, one of full_factorial, fractional_factorial, plackett_burman, central_composite. Required.
alphaNoalpha, value. Required.rotatable
factorsYesfactors, array. Required.
randomizeNorandomize, boolean. Required.
generatorsNogenerators, array. Optional.
replicatesNoreplicates, integer, from 1 to 100. Required.
centerPointsNocenterPoints, integer, from 0 to 1000. Required.

Output Schema

NameRequiredDescriptionDefault
runsNoruns. Number.
matrixNomatrix. Array.
aliasesNoaliases. Object.
sourcesNosources. Array.
resolutionNoresolution. Number.
limitationsNolimitations. Array.
definingRelationNodefiningRelation. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 useful non-annotated behaviour: a $0.03 USDC price, a POST endpoint, and critically that an unpaid call returns x402 payment terms instead of running — an agent trap it would otherwise hit. It also discloses the seeded xorshift128+ shuffle and cross-language reproducibility, though it does not describe output size or ordering guarantees beyond 'standard order'.

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?

Design capabilities are front-loaded in the first clause, followed by randomization behaviour, then pricing/transport as short factual fragments. No sentence is filler; each carries either capability, behaviour, or billing information an agent needs.

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 8 parameters documented at 100% coverage and an output schema present, the description need not explain return values, and it correctly spends its budget on payment gating and randomization semantics. The remaining gap is conditional parameter logic — e.g., that fractional factorials normally require `generators` — which an agent must infer.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by linking `seed` and `randomize` to a specific xorshift128+ algorithm whose results are reproducible across implementations, and by tying the design-family list to the `type` enum. It does not clarify what format `generators` strings take or how `alpha` interacts with `type`.

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 uses a specific verb (generate) plus a precise resource (designed experiments) and enumerates the four design families it produces — full factorial, fractional factorial, Plackett-Burman, central composite — matching the `type` enum. It is clearly distinguished from the analysis-oriented siblings by producing designs rather than analysing data, although no sibling is named explicitly.

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 rather than stated: the description notes randomization is optional and reproducible with a seed, and that an unpaid call does not execute. There is no guidance on when to choose full vs. fractional factorial, when generators are required, or how this tool fits before the analysis tools (e.g., effects-analyze).

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