Skip to main content
Glama

Conversion Rate Confidence Interval

bpj_conversion_confidence
Read-onlyIdempotent

Compute a 95% Wilson confidence interval for a conversion rate from independent binary observations.

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": {
      "successes": "<successes>",
      "trials": "<trials>"
    },
    "name": "bpj_conversion_confidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
trialsYes
successesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the interval is fixed at 95% (not a configurable parameter) and uses the Wilson method, which matters for small-sample results. It says nothing about what the response contains, which is a gap given there is no output schema.

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

Conciseness5/5

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

A single front-loaded sentence with no filler, immediately stating the method, the confidence level, and the input assumptions. Nothing could be removed without losing information.

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

Completeness2/5

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

For a tool with no output schema and zero schema description coverage, the description should state the shape of the result (point estimate plus lower/upper bounds) and the successes-vs-trials relationship. Neither is present, so an agent knows what the tool computes but not how to interpret or validate the call.

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%, so the description carries the full burden for the two parameters and does not meet it. It never explains that 'successes' is the count of positive outcomes, that 'trials' is the total, or that successes should not exceed trials, leaving the only real constraint to inference from the parameter names.

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 operation and statistic: compute a 95% Wilson confidence interval for a conversion rate. That is far more precise than a tautology and clearly separates it from the financial and text-processing siblings. It stops short of naming any sibling as an alternative, so it does not earn a 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 phrase 'from independent binary observations' implicitly states the applicability condition (binary outcomes, independence assumption), which is useful. However, there is no explicit when-to-use vs when-not guidance and no mention of alternatives such as a normal approximation or exact methods, so usage is only implied.

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.