Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Bio Target Base Rate (historical phase-progression rate, survivorship-complete)

bio_target_base_rate
Read-onlyIdempotent

Historical phase-advancement rate for a target gene — fraction of resolved programs that reached approval or were acquired-while-active, out of all resolved (positive + discontinued). Discontinuations ARE in the denominator — programs quietly dropped, delisted, shelved, OR that recorded a documented Phase-3 endpoint FAILURE (v2, from SEC trial-readout extraction) show up as negatives. Substrate: 21 years of 10-Ks across 1,676 CIKs, keeping programs from delisted / bankrupt / spun-out issuers.

⚠️ CRITICAL — NOT a trial-success rate, and the residual bias is CENSORING (conservative), not inflation. POSITIVE = approved or acquired-while-active. NEGATIVE = discontinued (company died, program dropped, or a documented Phase-3 miss). A program at a still-alive company still ADVANCING with no failure signal is CENSORED — excluded from the denominator entirely, NOT scored positive. So the metric never counts advancement as success; its residual bias is that it still censors un-resolved and earlier-phase / undisclosed failures, so it leans conservative-optimistic on targets with lots of live pipeline. v2 (methodology phase_progression_v2) closes the Phase-3-disclosed slice by reclassifying documented Phase-3 misses to discontinued (approved programs untouched). n_advanced in the response is always 0 (advanced = censored, never scored) — there is no non-zero case to discount. Read the returned methodology_note field for the canonical caveat text.

Pass exclude_cik to get the base rate after excluding the company being evaluated (e.g. 'how often do TTR programs advance for OTHER companies?'). Returns verdict: insufficient_priors when fewer than 3 priors. Resolve gene aliases with bio_entity_resolve first — wants the canonical HGNC symbol.

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": {
      "gene": "<gene>"
    },
    "name": "bio_target_base_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYesCanonical HGNC gene symbol (e.g. 'TTR', 'PDCD1', 'FOLH1'). Resolve aliases with bio_entity_resolve.
as_of_dateNoISO date — count only programs resolved on or before this date. Defaults to today.
exclude_cikNoIf given, scan program_outcomes excluding this CIK (the company being evaluated). Slower path but lets the caller ask 'rate for OTHER companies'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say read-only/idempotent/closed-world; the description adds substantial beyond that — the censoring direction of the residual bias, that advancing programs are excluded rather than scored positive, the v2 reclassification of disclosed Phase-3 misses, that n_advanced is structurally always 0, the slow path for exclude_cik, and where the canonical caveat text lives. This is exactly the kind of behavioral context a metric tool needs.

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

Conciseness3/5

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

The metric definition is correctly front-loaded in the first sentence, but the censoring/bias point is restated three times (the CENSORED paragraph, the 'residual bias' sentence, and the n_advanced-always-0 sentence), and bold/emoji emphasis inflates a 3-parameter read tool well past what it needs. It is not padded with filler, but it is materially longer than required.

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 no output schema, the description carries the return-value burden and does identify key response fields (verdict: insufficient_priors, n_advanced, methodology_note) plus the prior-count threshold. The full response shape (the actual rate fields, sample counts) is not enumerated, which is a minor gap for a metric tool but not a blocking one.

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 schema already documents all three parameters, including the HGNC-symbol and alias-resolution note that the description repeats. The only real addition is the framing of exclude_cik as 'how often do TTR programs advance for OTHER companies' and the insufficient-priors consequence, which is modest value over the schema. Baseline 3 is appropriate.

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?

The opening sentence names the exact metric — fraction of resolved programs reaching approval or acquired-while-active out of all resolved programs — for a specific resource (a target gene). It explicitly distinguishes itself from a trial-success rate, and the denominator/numerator definitions are unambiguous enough that an agent knows precisely what it will get.

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?

It gives concrete operational guidance: resolve aliases with bio_entity_resolve first, use exclude_cik for the 'other companies' framing, and expect verdict: insufficient_priors under 3 priors. It also warns what the metric is NOT (a trial-success rate), which functions as a when-not signal, but it never names an alternative tool to use instead for that other question.

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