Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Next FDA catalyst + how-to-think-about-it dossier (index with drill-down pointers)

bio_catalyst_dossier
Read-onlyIdempotent

The next FDA catalyst for a biotech, plus how to think about it — as an INDEX with drill-down pointers. One call returns the nearest PDUFA/AdCom date AND a compact headline for each context pillar (prior CRLs + the base rate for that reason, comparable historical approval setups with realized returns, management track record, manufacturing/inspection risk, pipeline) — each with an exact drill tool call to go deeper. Read the index, then follow the drill for whichever pillar matters to your question; each drilled tool surfaces its own detail (and often its own pointers).

Real-time fan-out over already-cooked data (base rates, PIT snapshots, CRL reasons, the people graph are all pre-computed) — nothing baked ahead, nothing stale. Token-cheap by design: headline + pointer per pillar, NOT the full record of each.

Inputs: ticker_or_cik (required), as_of (YYYY-MM-DD — PIT gate for the CRL/pipeline/comparables reads; default today).

Each pillar carries its headline fields + drill (the ready next call) + available (false when that read errored or is empty — the drill still works). Pillars: next_catalyst · prior_crls · crl_base_rate (for the most-recent prior reason) · target_base_rate (the target's historical approval base rate — the key prior for an AdCom efficacy question) · comparable_approvals · management · manufacturing_risk · pipeline. next_catalyst carries source_accession + filing_url; prior_crls carries most_recent_accession + most_recent_filing_url when that CRL was disclosed in an SEC filing.

Caveat: the drill calls are the source of truth for detail — the dossier headlines are deliberately lossy summaries. Approval-anchored comparable returns are YES-arm only (see bio_similar_setups); CRL absence isn't proof of none (see bio_prior_crl_reason).

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_catalyst_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoISO date YYYY-MM-DD — PIT gate for CRL/pipeline/comparable reads. Default: today.
ticker_or_cikYesBiotech ticker (Atlas-resolved) or SEC CIK. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description adds genuinely non-structured context: the fan-out is over pre-computed data, per-pillar `available` flags go false on errored reads while drills still work, and it discloses a data-quality caveat (YES-arm-only comparable returns, CRL absence not proof of none). No output schema exists, and while the pillar list and carried accession/URL fields are described, the exact headline field names per pillar are not.

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?

Bold headers, inputs, pillar enumeration and caveats are front-loaded and skimmable, and the read-index-then-drill instruction is placed early. Some phrasing is promotional filler ('nothing baked ahead, nothing stale', 'already-cooked data') that could be cut without losing information.

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

Completeness5/5

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

For an eight-pillar aggregator with no output schema, the description carries the full burden and does it: it enumerates every pillar, names the extra keys each carries (`drill`, `available`, `source_accession`, `filing_url`), and scopes returns as deliberately lossy with drills as the escape hatch. Nothing an agent needs to call it or interpret the index is missing.

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% and both parameters are documented there, so the description's restatement of `ticker_or_cik` (required) and `as_of` (PIT gate, default today) adds little beyond the schema. It does clarify that `as_of` gates specifically the CRL/pipeline/comparables reads, a marginal semantic gain.

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 deliverable ('nearest PDUFA/AdCom date AND a compact headline for each context pillar') and explicitly frames itself as an INDEX with drill pointers, so an agent can tell it apart from detail tools like bio_prior_crl_reason and bio_similar_setups, both of which it names.

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?

Gives a clear operating pattern: 'Read the index, then follow the drill for whichever pillar matters to your question,' and warns that drills are the source of truth while headlines are lossy. It does not explicitly say when to reach for this vs. siblings like catalyst_calendar or bio_fda_approvals, so it stops short of full alternative routing.

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