Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Fit a life distribution to censored data

statistics_weibull-reliability
Read-onlyIdempotent

Maximum-likelihood Weibull, lognormal or exponential life fits to right-censored failure data with Fisher-matrix confidence bounds, B-lives, reliability at chosen times and mean time to failure. Price $0.05 USDC. POST /api/v1/statistics/weibull-reliability. An unpaid call returns the x402 payment terms and does not run.

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": {
      "times": "<times>",
      "failed": "<failed>"
    },
    "name": "statistics_weibull-reliability"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesYestimes, array. Required.
bLivesNobLives, array. Required.
failedYesfailed, array. Required.
confidenceNoconfidence, number. Required.
distributionNodistribution, string, one of weibull, lognormal, exponential. Required.weibull
reliabilityAtNoreliabilityAt, array. Required.

Output Schema

NameRequiredDescriptionDefault
mttfNomttf. Number.
bLivesNobLives. Array.
sourcesNosources. Array.
censoredNocensored. Number.
failuresNofailures. Number.
confidenceNoconfidence. Number.
parametersNoparameters. Object.
limitationsNolimitations. Array.
parameterCiNoparameterCi. Object.
reliabilityNoreliability. Array.
distributionNodistribution. String.
logLikelihoodNologLikelihood. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds what they cannot: the operation costs $0.05 USDC, is reached via POST /api/v1/statistics/weibull-reliability, and an unpaid call returns x402 payment terms without executing. That payment-gating disclosure is essential pre-invocation context an agent would otherwise discover only by failing.

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?

Three dense sentences, front-loaded with the capability, followed by cost and transport, then the failure mode of an unpaid call. No filler, no restatement of the title, and the critical caveat arrives before invocation.

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

Completeness4/5

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

An output schema exists, so return values needn't be spelled out, and the description covers the modelling choice and the payment behavior. What is missing for a censored-data estimator is the domain contract: that 'times' and 'failed' are parallel arrays, that 1 means failure and 0 means censored, and that bLives/reliabilityAt are evaluated on the same time axis.

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%, so the baseline is 3; however the schema descriptions are near-empty labels ('bLives, array. Required.'). The description does add meaning by tying the outputs to specific parameters — B-lives for bLives and 'reliability at chosen times' for reliabilityAt — which is genuine value beyond the schema. It does not explain the 0/1 censoring indicator encoding of 'failed' or the required alignment/units of times versus reliabilityAt, so it does not fully compensate.

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?

Names a specific technique and resource: maximum-likelihood Weibull/lognormal/exponential life fits to right-censored failure data, and enumerates the outputs (Fisher-matrix confidence bounds, B-lives, reliability at chosen times, MTTF). An agent can immediately tell this is a survival/reliability fitting tool, distinct from the hypothesis-test and regression siblings.

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?

The phrase 'right-censored failure data' establishes the applicable data context, and the endpoint verb signals this is a computation over supplied arrays rather than a lookup. It stops short of explicit when-to-use/when-not guidance or naming an alternative for complete (uncensored) data, so it is clear context without exclusions.

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