Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Bio Risk Score (composite de-risking — magnitude/sizing, NOT direction)

bio_risk_score
Read-onlyIdempotent

Composite de-risking score for a biotech company at a point in time — a single number summarizing pipeline-breadth × has-approved-drug × runway × partnership × target-crowdedness, validated against catalyst-day |returns|.

⚠️ MAGNITUDE / SIZING signal — NOT a direction predictor. Higher score = more de-risked = smaller expected |moves|. Does NOT say which direction the stock will go. Use for sizing / vol bands / options input. The methodology caveat is in the response — carry it into any brief that quotes the number.

Returns the latest score ≤ as_of_date with components (n_assets, runway_quarters, has_approved, log_market_cap, max_target_crowdedness, partnership_present) and source_refs (which inputs the score was joined from).

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": {
      "ticker_or_cik": "<ticker_or_cik>"
    },
    "name": "bio_risk_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_of_dateNoISO date (YYYY-MM-DD). Returns the latest score ≤ this date. Defaults to today.
ticker_or_cikYesCompany ticker (e.g. 'BBIO') or CIK integer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 still adds real behavior: the score is validated against catalyst-day |returns|, the returned row is the latest ≤ as_of_date, components and source_refs come back, and a methodology caveat is embedded in the response that must be carried forward. That last point is a usage obligation an agent could not infer from structure alone.

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?

Front-loaded with the definition, then the disambiguation warning, then the return contract — a sensible order. There is some duplication between the title and the ⚠️ block ('MAGNITUDE / SIZING — NOT direction' appears twice), but the redundancy is defensible for a high-stakes misinterpretation risk.

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?

No output schema exists, and the description compensates by naming the returned components and source_refs plus the caveat, which is what an agent needs before quoting the number. Minor gap: no statement about what happens when no score exists before as_of_date or for an unresolved ticker.

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 both parameters are already documented in the schema, including the '≤ this date' semantics. The description restates the as_of_date behavior and the ticker/CIK identifier role but adds no format, edge-case, or defaults detail beyond structured fields — baseline 3.

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?

States a specific artifact — a composite de-risking score for a biotech at a point in time — and enumerates the exact inputs that compose it (pipeline breadth, has-approved, runway, partnership, target crowdedness). It also draws a hard boundary against direction prediction, which is the main confusion an agent could have with sibling risk/analysis tools.

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?

Explicit when-to-use ('sizing / vol bands / options input') and explicit when-not ('NOT a direction predictor', 'does NOT say which direction the stock will go'). The gap is that it never names a sibling to route to for direction (e.g. a catalyst or readout tool), leaving the alternative implicit.

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