Skip to main content
Glama

Compute a sample size

compute_sample_size

Recommend a sample size for a control using its frequency, risk, and population size, with a documented rationale.

Instructions

Recommend a sample size for a control from its frequency, risk and population size, with a documented rationale.

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": {
      "frequency": "<frequency>"
    },
    "name": "compute_sample_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
riskNomoderate
frequencyYes
populationSizeNo
priorDeficiencyNo
externalRelianceNo

Output Schema

NameRequiredDescriptionDefault
cappedYes
frequencyYes
rationaleYes
recommendedYes
effectiveRiskYes
requestedRiskYes
populationSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully signals the output includes a 'documented rationale,' but says nothing about the sizing methodology, whether results are deterministic, how defaults behave, or permission requirements. Some added value, but far from complete for a computation tool.

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 core action and its drivers come first. It is efficient, though the brevity is also the source of the coverage gaps rather than pure conciseness.

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?

The existence of an output schema excuses the description from explaining return values, and the core purpose is legible. However, for a 5-parameter computation tool with zero annotation or schema-description coverage, the definition leaves meaningful inputs and behavior unaddressed.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters. The description names only frequency, risk, and population size, and omits priorDeficiency and externalReliance — two modifiers that materially change the recommendation. An agent reading only this text would not know those inputs influence the result.

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 states a specific verb and resource ('Recommend a sample size for a control') plus the determining inputs (frequency, risk, population size), which cleanly separates it from the sibling select_sample. It stops short of explicitly differentiating itself from that sibling or explaining whether it selects versus merely sizes.

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 only implied: the phrasing 'for a control from its frequency, risk and population size' suggests you must already have control frequency/risk data, but no when-to-use, prerequisites, or alternatives (e.g., the relationship to select_sample) are given. This is minimum viable context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.