Skip to main content
Glama

Statistical analysis plan checker

submit_statistics_plan_checker
Idempotent

Check a pre-registered analysis plan for completeness and internal consistency before data is collected: the registration identifier, primary outcome, sample size, alpha, power, randomisation, blinding, analysis population, missing-data handling and statistical method, plus uncontrolled multiplicity when several endpoints are named. Before data collection, to catch a plan that is incomplete or internally inconsistent. Do not choose this when you need the power calculation verified against an effect size, which needs the numbers. Example requests: Check my statistical analysis plan before I collect data. | Does my analysis plan state power, alpha and the multiplicity adjustment? | What is missing from this pre-registered analysis plan? | Run a statistical analysis plan check over this protocol.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_statistics_plan_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context about what the check inspects and its limits, but it never mentions that this is a priced capability requiring a quote_id and authorized_by, nor that readOnlyHint=false means a job is actually created and a price accepted — a significant omission for an agent deciding whether to call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a dense, useful front-loaded enumeration. However, the second sentence ('Before data collection, to catch a plan that is incomplete or internally inconsistent') largely restates the opening clause, and four example requests are more than this simple single-input tool needs, so the definition is longer than its content warrants.

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?

An output schema exists, so return-value detail is rightly omitted, and the description covers scope, timing and exclusions thoroughly for a one-artifact checker. The only real gap is the quote/authorization workflow, which is documented in the input schema rather than the description, keeping this just short of complete.

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 coverage is 75%, so the baseline is 3. The description's enumeration of checked elements implicitly tells the agent what the analysis_plan text should contain, which is modest added meaning, but it says nothing about the analysis_plan format beyond what the schema states and nothing at all about quote_id, authorized_by or accepted_price.

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?

Names a specific verb and resource ('Check a pre-registered analysis plan') and enumerates the exact dimensions inspected (registration identifier, primary outcome, sample size, alpha, power, randomisation, blinding, analysis population, missing-data handling, statistical method, multiplicity). The scope is narrow and unmistakable, and it is clearly distinguishable from sibling validators like submit_backtest_overfitting_check or submit_model_card_generator.

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

Usage Guidelines5/5

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

Gives an explicit timing condition ('before data is collected') and an explicit exclusion ('Do not choose this when you need the power calculation verified against an effect size, which needs the numbers'), which routes the agent away from an adjacent but unsupported use case. Four example requests reinforce the intended invocation context.

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