Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

Cox proportional hazards regression

predictive-analytics_cox-regression
Read-onlyIdempotent

Maximise the Cox partial likelihood with Efron or Breslow ties, return hazard ratios with SEs, concordance, and a rank-time proportional-hazards check. Price $0.05 USDC. POST /api/v1/predictive-analytics/cox-regression. 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_cox-regression"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiesNoties, string, one of efron, breslow. Required.efron
subjectsYessubjects, array. Required.
confidenceNoconfidence, number. Required.

Output Schema

NameRequiredDescriptionDefault
phTestNophTest. Array.
sourcesNosources. Array.
convergedNoconverged. Boolean.
concordanceNoconcordance. Number.
limitationsNolimitations. Array.
coefficientsNocoefficients. Array.
logLikelihoodNologLikelihood. Number.

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 read-only, idempotent, open-world, and non-destructive behavior. The description adds important operational context beyond annotations: the $0.05 USDC price, the POST endpoint, and that unpaid calls return x402 payment terms without running. It does not discuss auth details or error handling, but it discloses the key payment/failure-mode behavior.

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?

Front-loads the statistical operation and then supplies payment and endpoint facts in compact sentences. There is no superfluous wording; each sentence provides either methodological or operational information.

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?

Given the rich input schema and the existence of an output schema, the description supplies the essential computation summary, cost, endpoint, and unpaid-call behavior. It remains thin on usage selection versus survival alternatives, but is otherwise sufficient for correct invocation.

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 description coverage is 100%, including the nested subject fields, ties enum, and confidence bounds, so the schema carries the parameter documentation. The description mentions ties and outputs but adds little meaning beyond the schema, making the baseline 3 appropriate.

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?

States a specific computation, maximising the Cox partial likelihood with Efron or Breslow ties, and specific return objects including hazard ratios, SEs, concordance, and a proportional-hazards check. The purpose is clear, but the description does not distinguish when to choose this over the sibling Kaplan-Meier survival tool.

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?

Provides no when-to-use, when-not-to-use, or alternative-selection guidance. It describes mechanics, cost, and endpoint behavior, but leaves the choice between Cox regression and Kaplan-Meier survival analysis to the agent.

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