Skip to main content
Glama

nci_biomarker_searcher

Search the NCI Clinical Trials database for biomarkers used in eligibility criteria, aiding precision medicine by identifying specific gene mutations, protein expressions, and molecular markers for targeted patient selection.

Instructions

Search for biomarkers in the NCI Clinical Trials database.

Searches for biomarkers used in clinical trial eligibility criteria.
This is essential for precision medicine trials that select patients
based on specific biomarker characteristics.

Biomarker examples:
- Gene mutations (e.g., BRAF V600E, EGFR T790M)
- Protein expression (e.g., PD-L1 ≥ 50%, HER2 positive)
- Gene fusions (e.g., ALK fusion, ROS1 fusion)
- Other molecular markers (e.g., MSI-H, TMB-high)

Requires NCI API key from: https://clinicaltrialsapi.cancer.gov/

Note: Biomarker data availability may be limited in CTRP.
Results focus on biomarkers used in trial eligibility criteria.

Example usage:
- Search for PD-L1 expression biomarkers
- Find trials requiring EGFR mutations
- Look up biomarkers tested by NGS
- Search for HER2 expression markers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoNCI API key. Check if user mentioned 'my NCI API key is...' in their message. If not provided here and no env var is set, user will be prompted to provide one.
biomarker_typeNoType of biomarker ('reference_gene' or 'branch')
nameNoBiomarker name to search for (e.g., 'PD-L1', 'EGFR mutation')
pageNoPage number (1-based)
page_sizeNoResults per page

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds important context: the requirement for an NCI API key with specific source URL, limitations ('Biomarker data availability may be limited in CTRP'), and scope clarification ('Results focus on biomarkers used in trial eligibility criteria'). It doesn't mention rate limits, authentication errors, or response formats, but covers key operational constraints.

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?

The description is well-structured and appropriately sized. It front-loads the core purpose, then provides context, examples, requirements, limitations, and usage examples. Some sentences could be more concise (e.g., the biomarker examples list is detailed but necessary), but overall it's efficient with minimal waste.

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?

Given the tool's complexity (biomarker search with API requirements), no annotations, but with 100% schema coverage and an output schema present, the description is reasonably complete. It covers purpose, context, requirements, limitations, and examples. The output schema existence means it doesn't need to explain return values, and it addresses key behavioral aspects despite no annotations.

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%, so the schema already documents all 5 parameters thoroughly. The description adds value through biomarker examples that help interpret the 'name' parameter, but doesn't provide additional semantics for parameters like 'biomarker_type' beyond what's in the schema. Baseline 3 is appropriate when schema does heavy lifting.

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 description clearly states the tool's purpose: 'Search for biomarkers in the NCI Clinical Trials database' and specifies 'Searches for biomarkers used in clinical trial eligibility criteria.' It distinguishes from siblings like 'nci_disease_searcher' or 'trial_searcher' by focusing specifically on biomarkers, not diseases or trials themselves.

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?

The description provides clear context for when to use this tool: 'essential for precision medicine trials that select patients based on specific biomarker characteristics' and gives example use cases. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings for different search needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/genomoncology/biomcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server