Skip to main content
Glama

recommend_test

Read-onlyIdempotent

Find the right statistical test by describing your data's outcome type, group count, and pairing. Receive a recommendation, reason, and alternative tests to consider.

Instructions

Not sure which rigor tool fits your question? Answer a few characteristics of the data and get back which tool to call, why, what to call instead if this test's assumptions look shaky, and what to run alongside it (an effect size, a power calculation, a natural follow-up). Every test in this package already documents this guidance in its own docstring for the sibling comparisons it knows about -- this tool exists so you don't have to have already read every other tool's docstring to find the one relevant cross-reference. Pure decision logic, no statistics computed here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairedNofor n_groups=2 (continuous/rank_or_ordinal/proportion): were the same subjects measured twice, rather than two independent groups?
n_groupsNo1 = one sample vs. a hypothesized value; 2 = two groups/conditions; 3+ = three or more groups. Ignored when testing_association=true.
outcome_typeYeswhat kind of thing is being compared/measured: "continuous" (means), "proportion" (rates), "count_or_category" (category counts / contingency tables), or "rank_or_ordinal" (ordinal data -- always routed to a rank-based test)
small_or_skewedNois the sample small, visibly skewed, or outlier-heavy? nudges toward the non-parametric alternative
testing_associationNothis is "does x relate to/predict y" for two continuous or ranked variables, not a group comparison -- routes to correlation/regression instead
two_categorical_variablesNofor outcome_type="count_or_category": testing association between two categorical variables (a contingency table) rather than counts against an expected distribution?

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already disclose that the tool is read-only, non-destructive, and idempotent, so the bar shifts. The description adds valuable behavioral context: it returns reasoning, alternatives, and follow-up recommendations, while performing no statistical computation. This is consistent with the annotations and gives agents a richer model of the 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?

The description is front-loaded with the user's decision problem and remains focused throughout. The sentence about existing docstrings is slightly showy but makes the tool's role clearer, so it still earns its place; overall the length is appropriate.

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

Completeness5/5

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

Even without an output schema, the description enumerates exactly what the agent will get back: which tool to call, why, what to call instead if assumptions look shaky, and what to run alongside. Combined with the complete parameter schema and safety annotations, this gives the agent a well-rounded picture of this small decision-only tool.

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 100%, so the input schema already explains all six parameters and their defaults. The description only refers to them generically as 'a few characteristics of the data' and does not add per-parameter meaning, which matches the baseline 3 for high schema coverage.

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 clearly identifies the tool as a decision/recommendation layer: it answers which statistical tool to call based on data characteristics. It also differentiates itself from every sibling statistical tool by saying it is 'pure decision logic, no statistics computed here.'

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

Usage Guidelines4/5

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

It explicitly states when to use the tool: whenever the user is unsure which rigor tool fits their question. It also explains the value proposition over reading every sibling docstring, and implies the tool should not be used for actual statistical computation; however, it does not explicitly list 'when not to use' in a formal way.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrnh/rigor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server