Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Bio Landscape (every company with a target / indication, as-of date)

bio_landscape
Read-onlyIdempotent

Find every company with a drug asset targeting a gene (axis='gene') or treating an indication (axis='indication'), as of a date — with source filings cited. The cross-sectional companion to bio_pipeline (which is one-company-over-time).

Returns one row per (company, asset) so a single company with three assets against the target appears three times. Pre-resolve gene aliases (PD-1, HER2) with bio_entity_resolve first — landscape wants the canonical symbol (PDCD1, ERBB2). Indication matching (updated 2026-06-15): packed canonicals like 'immunoglobulin a nephropathy (igan), primary membranous nephropathy (pmn), focal segmental glomerulosclerosis (fsgs), …' are now exploded at build time in super-bio's pipeline_snapshots_by_indication matview, so an exact match on any single disease (e.g. 'immunoglobulin a nephropathy (igan)') finds every company whose canonical includes it. Original packed string is preserved as indication_packed_canonical for display. Tier-3 disease ontology (Cancer / Oncology / Solid tumors unification) is still future work on the super-bio side.

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": {
      "axis": "<axis>",
      "value": "<value>"
    },
    "name": "bio_landscape"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisYesFilter axis: 'gene' = exact match on canonical HGNC symbol; 'indication' = case-insensitive substring (ILIKE) match against the exploded canonical disease name. Use specific terms for indication (e.g. 'non-small cell lung cancer', 'iga nephropathy') — short queries like 'cancer' will match very broadly.
valueYesThe gene symbol (e.g. 'PDCD1') or indication canonical (e.g. 'transthyretin amyloid cardiomyopathy (attr-cm)').
as_of_dateNoISO date (YYYY-MM-DD). Return each company's latest snapshot ≤ this date. Defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read-only idempotent non-destructive operation, so the description correctly focuses on behavior beyond safety. It discloses the critical row-granularity behavior (one row per company/asset, causing expected duplication), that source filings are cited, and how indication canonicals are exploded and preserved.

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?

Purpose and the sibling contrast are front-loaded, and most sentences carry useful operational detail. The description is somewhat dense and includes update/future-work notes and markdown emphasis that add length, but it remains readable and largely earns its space.

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?

There is no output schema, so the description appropriately explains the return shape: one row per company/asset with source filings cited. It also covers the main matching edge cases, alias handling, and the known ontology limitation, leaving no essential invocation detail missing for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by telling the agent to pre-resolve aliases into canonical HGNC symbols and by explaining the indication matching and packed-canonical preservation in more operational detail than the schema fields provide.

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 verb and resource: find every company with a drug asset targeting a gene or treating an indication, as of a date. It explicitly distinguishes itself from bio_pipeline as the cross-sectional companion versus one-company-over-time, and names bio_entity_resolve for alias pre-resolution, so the agent can tell it apart from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts its use with bio_pipeline and instructs the agent to pre-resolve gene aliases with bio_entity_resolve first. It also gives clear indication-matching guidance, including the build-time explosion behavior and the current limits of tier-3 disease ontology unification.

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