Skip to main content
Glama

BRAINIAC A/B Testing & Experimentation Statistics

Assign units to experiment groups deterministically

experimentation_bucket-assign
Read-onlyIdempotent

Stateless SHA-256 bucketing of unit ids into an experiment with traffic gating, ordered group shares and an optional layer, documented so any SDK can reproduce it. Price $0.01 USDC. POST /api/v1/experimentation/bucket-assign. 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": {
      "unitIds": "<unitIds>",
      "experiment": "<experiment>"
    },
    "name": "experimentation_bucket-assign"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNolayer, value. Optional.
unitIdsYesunitIds, array. Required.
experimentYesexperiment, object. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
algorithmNoalgorithm. String.
assignmentsNoassignments. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses substantial behavioral context: statelessness, determinism via SHA-256, traffic gating, ordered group shares, an optional layer, the POST endpoint, and critically that an unpaid call returns x402 terms of $0.01 USDC and does not execute.

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 core mechanism in the first sentence, followed by the payment and endpoint essentials in two short sentences. Every clause carries information, though the endpoint path is largely derivable from the tool name and adds marginal weight.

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, return formatting need not be described, and the nested experiment/layer/groups structure is captured at a high level. Payment and idempotency behavior are covered, so an agent has enough to invoke correctly; minor gaps remain around edge cases such as duplicate unit ids or layer/experiment consistency.

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 baseline is 3, but the description adds real semantics the schema lacks: that group shares are ordered (order affects bucketing), that a layer is optional and constrains assignment, and that traffic gating governs inclusion. It does not explain how trafficShare interacts with group shares, leaving a small gap.

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 states a specific verb and resource — SHA-256 bucketing of unit ids into an experiment — and names the distinguishing mechanisms (traffic gating, ordered group shares, optional layer). This differentiates it from siblings like experimentation_bandit-allocate or experimentation_flag-rule-evaluate without needing to open the schema.

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 'deterministic' and 'stateless ... so any SDK can reproduce it', which signals a deterministic assignment tool rather than an adaptive allocator, but the description never explicitly says when to prefer this over bandit-allocate or flag-rule-evaluate. No exclusions or prerequisites for the caller beyond the payment note are 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