Skip to main content
Glama

Monte statistics

Is this test result real?

test_result
Read-onlyIdempotent

For a positive result, the chance you really have the thing, from how common it is, how often the test catches it and how often it false-alarms (Bayes).

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": {
      "how_common": "<how_common>",
      "catches": "<catches>",
      "false_alarms": "<false_alarms>"
    },
    "name": "test_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
catchesYesSensitivity: chance the test is positive when you have it, 0 to 1
how_commonYesBase rate, 0 to 1, like 0.01 for 1 in 100
false_alarmsYesChance the test is positive when you do not have it, 0 to 1

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 this a read-only, idempotent, non-destructive, closed-world operation, so safety is covered. The description adds that the computation is Bayesian and instant, but it omits that the returned value is a probability between 0 and 1, leaving the output shape to inference.

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 that states the result first and the inputs after, with no filler. 'The thing' and 'it' are informal and slightly ambiguous, which is the only thing keeping it below a 5.

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?

Three required, fully described parameters and no output schema make this a simple tool. Still, the description does not state the output scale (a 0–1 probability) or that only positive-test scenarios are handled, which an agent would want before calling.

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 100% and each parameter already carries a precise definition, so the schema does the heavy lifting. The description's plain-language phrases ('how common it is', 'how often the test catches it', 'how often it false-alarms') loosely map to the three inputs but add no numerical format or edge-case detail beyond the schema.

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 the specific computation: the probability you actually have the condition given a positive test, derived from base rate, sensitivity, and false-positive rate. It signals the Bayesian method, which separates it from generic computation siblings like solve. It is phrased as a description of the answer rather than an action verb, which slightly blunts it.

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?

'For a positive result' implies the scenario in which the tool applies, but there is no guidance on when to use it versus alternatives such as solve or ab_test, no exclusions, and no note that it does not cover negative results.

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