Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Bio Target Trajectory (quarterly crowdedness + max-phase time series)

bio_target_trajectory
Read-onlyIdempotent

Quarterly trajectory for a target gene: how many companies and how many assets have been pursuing it each quarter, the maximum clinical phase reached, and the top-ranked companies at each point. Use to answer 'is this target getting more crowded?' or 'when did Phase-3 work on this target peak?' Pass a canonical gene symbol; resolve aliases first with bio_entity_resolve.

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

Input Schema

NameRequiredDescriptionDefault
geneYesCanonical HGNC gene symbol (e.g. 'PDCD1', 'TTR'). Resolve aliases via bio_entity_resolve.
compactNoIf true, drop the per-quarter `top_companies` list to shrink the payload ~7× (35KB → ~5KB per gene). Use when you only need the n_companies / n_assets / max_phase trend.
end_dateNoISO date (YYYY-MM-DD). Latest year_quarter. Defaults to no upper bound.
start_dateNoISO date (YYYY-MM-DD). Earliest year_quarter to include. Defaults to no lower bound.
last_n_quartersNoConvenience window: return only the most recent N quarters (overrides start_date if both given, ignores end_date). 12 = 3 years, 20 = 5 years. Omit for the full series.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), so the description's job is to describe the content of the result, which it does by enumerating the per-quarter fields returned. It does not mention how quarters are labeled, how max_phase is encoded, or behavior for targets with no activity, leaving minor gaps.

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?

Two sentences, front-loaded with what the series contains, followed by the question it answers and the alias-resolution prerequisite. Every clause carries information; nothing is filler.

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 usefully enumerates the returned fields, and annotations handle safety, so an agent can decide whether to call it. Small remaining gaps are the exact form of the quarter keys and phase values, which the agent will discover from the payload.

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%, and each parameter already carries its own description including the compact payload tradeoff and the last_n_quarters override semantics. The description only repeats the canonical-symbol prerequisite that the schema's gene field already states, so it adds essentially nothing beyond the schema.

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 specific resource and metric set: a quarterly time series of company counts, asset counts, maximum clinical phase, and top-ranked companies per quarter for a target gene. It is clearly not a snapshot tool, which differentiates it in spirit from siblings like bio_target_base_rate, though no sibling is named outright.

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 two concrete example questions that select this tool ('is this target getting more crowded?', 'when did Phase-3 work on this target peak?') and states a required precondition: resolve aliases via bio_entity_resolve before calling. No explicit when-not guidance or named alternative is provided.

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