Skip to main content
Glama

Experiment Cohort Allocation

bpj_experiment_cohort_allocation
Read-onlyIdempotent

Reserve a whole-person holdout first, then split the remaining audience between treatment and control while preserving the total.

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": {
      "sample": "<sample>",
      "excluded": "<excluded>",
      "groupShare": "<groupShare>"
    },
    "name": "bpj_experiment_cohort_allocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
sampleYes
excludedYes
groupShareYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the ordering of operations (holdout reserved first, remainder split second) and the invariant that the total is preserved. It omits edge-case behavior, such as what happens if the holdout and treatment shares exceed 100 or how fractional people are rounded.

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?

A single front-loaded sentence with no filler; the sequence of operations is stated in execution order. It is dense but every clause carries information, so there is little to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter deterministic calculator with solid annotations and no output schema, the description covers the core algorithm and invariant, which is the main thing an agent needs. It falls short on constraint handling (share totals above 100) and on rounding semantics for whole-person allocation, both of which materially affect results.

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 0%, so the description must carry parameter meaning, and it does partially: 'whole-person holdout' maps to excluded, 'split the remaining audience between treatment and control' maps to groupShare, and 'preserving the total' maps to sample. However, it never ties these concepts to the parameter names or units, and it leaves ambiguous whether groupShare is a percentage of the original sample or of the post-holdout remainder — a distinction the schema titles do not resolve either.

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 operation (reserve a holdout, then split the remainder into treatment and control) and its invariant (total preserved), which is far more than a restatement of the title. It does not explicitly differentiate from siblings, though the siblings listed are unrelated allocation/codec utilities, so confusion risk is low.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites, and no mention of how this differs from any alternative. The agent learns what the tool computes but nothing about the conditions under which it should be selected over another tool.

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.