Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

Kaplan-Meier survival curves and log-rank test

predictive-analytics_kaplan-meier-survival
Read-onlyIdempotent

Estimate group Kaplan-Meier curves with Greenwood log-log confidence intervals, median survival, survival at chosen times, and a multi-group log-rank test. Price $0.04 USDC. POST /api/v1/predictive-analytics/kaplan-meier-survival. 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": {
      "subjects": "<subjects>"
    },
    "name": "predictive-analytics_kaplan-meier-survival"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoat, array. Optional.
subjectsYessubjects, array. Required.
confidenceNoconfidence, number. Required.

Output Schema

NameRequiredDescriptionDefault
groupsNogroups. Array.
logRankNologRank. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral facts: a $0.04 USDC price, the POST endpoint, and the important failure mode that an unpaid call returns payment terms instead of executing. It does not mention rate limits or sample-size failure behavior, but return shape is covered by the 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.

Conciseness4/5

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

Three tight sentences: capability first, then price and endpoint, then the payment-failure caveat. Every sentence carries information an agent needs. The endpoint path is somewhat redundant with the tool name but supports the payment context, so it is not wasteful enough to penalize further.

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?

With only three parameters, full schema coverage, and an output schema handling return values, the description covers method, cost, and the unpaid-call behavior. Minor gaps remain around input units and error conditions beyond payment, but nothing essential for a correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description goes modestly beyond the schema by linking the `at` parameter to "survival at chosen times" and explaining that confidence intervals are Greenwood log-log, which tells the agent what the `confidence` parameter actually controls. It still does not state the time unit or how groups map to separate curves.

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 precise verb and resource: estimate Kaplan-Meier curves with Greenwood log-log confidence intervals, median survival, survival at chosen times, and a multi-group log-rank test. That is far more specific than typical analytics-tool blurbs and clearly separates it from classification-metrics or pca. It stops short of naming the nearest sibling (cox-regression) as an alternative, so it is clear but not sibling-differentiating.

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?

There is no guidance on when to choose this over the cox-regression sibling, nor any stated data prerequisites (censoring assumptions, minimum group sizes). The only conditional statement concerns payment — an unpaid call returns x402 terms and does not run — which is operational rather than selection guidance. Usage must be inferred from the statistical capability alone.

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