Skip to main content
Glama

Monte statistics

Did my change really work?

ab_test
Read-onlyIdempotent

Two-proportion z test for an A/B test: the two rates, the lift, the p-value, a 95% range for the difference, and visitors needed per version to detect this gap.

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": {
      "visitors_a": "<visitors_a>",
      "conversions_a": "<conversions_a>",
      "visitors_b": "<visitors_b>",
      "conversions_b": "<conversions_b>"
    },
    "name": "ab_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
visitors_aYes
visitors_bYes
conversions_aYes
conversions_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description usefully discloses the return payload since no output schema exists, but it omits behavioral preconditions — notably that conversions cannot exceed visitors and that both visitor counts must be positive — and says nothing about how invalid inputs are handled.

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, and the method plus output list is packed efficiently. The colon-and-list structure reads well, though it front-loads outputs rather than the task's preconditions.

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 pure computation tool with no output schema, describing the returned metrics is the right instinct and is done well. However, with four undocumented required parameters and unstated input validity rules, the definition is not quite complete enough for an agent to call it correctly on the first try.

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% and all four parameters are required, so the description carries the full documentation burden. It adds no mapping of visitors_a/conversions_a/visitors_b/conversions_b to control vs. variant, no unit or constraint notes, and no clarification of the implicit conversions ≤ visitors relationship.

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 statistical method ('two-proportion z test') and enumerates the concrete outputs (rates, lift, p-value, 95% range, required sample size), so an agent knows exactly what computation happens. It does not explicitly contrast itself with siblings like test_result or solve, which keeps it at 4 rather than 5.

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?

The title 'Did my change really work?' and the mention of an A/B test imply the use case, so an agent can infer this is for comparing two conversion rates. There is no explicit when-to-use/when-not-to-use guidance, no mention of sample-size prerequisites, and no routing to an alternative 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.

Resources