Skip to main content
Glama

nci_organization_searcher

Search the NCI Clinical Trials database to find organizations involved in cancer research, including academic centers, hospitals, and sponsors. Use name, location, or type filters to retrieve results. Requires NCI API key.

Instructions

Search for organizations in the NCI Clinical Trials database.

Searches the National Cancer Institute's curated database of organizations
involved in cancer clinical trials. This includes:
- Academic medical centers
- Community hospitals
- Industry sponsors
- Government facilities
- Research networks

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

IMPORTANT: To avoid API errors, always use city AND state together when searching by location.
The NCI API has limitations on broad searches.

Example usage:
- Find cancer centers in Boston, MA (city AND state)
- Search for "MD Anderson" in Houston, TX
- List academic organizations in Cleveland, OH
- Search by organization name alone (without location)

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.
cityNoCity where organization is located. IMPORTANT: Always use with state to avoid API errors
nameNoOrganization name to search for (partial match supported)
organization_typeNoType of organization (e.g., 'Academic', 'Industry', 'Government')
pageNoPage number (1-based)
page_sizeNoResults per page
stateNoState/province code (e.g., 'CA', 'NY'). IMPORTANT: Always use with city to avoid API errors

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 full burden and does well by disclosing critical behavioral traits: API key requirement with source URL, API limitations on broad searches, and the important constraint about city+state pairing to avoid errors. It also provides concrete usage examples showing expected query patterns.

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?

The description is well-structured and appropriately sized. It starts with the core purpose, then provides context about what's searched, followed by critical requirements and constraints, and ends with concrete examples. Every sentence serves a clear purpose with zero wasted content.

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 (7 parameters, API integration) and the presence of an output schema, the description provides strong context about the database scope, API requirements, and usage patterns. The main gap is lack of explicit differentiation from sibling tools like nci_organization_getter, but overall it's quite complete for a search tool.

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 baseline is 3. The description adds some value by reinforcing the city+state constraint mentioned in the schema and providing example usage patterns, but doesn't significantly enhance parameter understanding beyond what the schema already documents.

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 searches for organizations in the NCI Clinical Trials database, specifying the exact resource (organizations) and database (NCI Clinical Trials). It distinguishes from siblings like nci_organization_getter by emphasizing search functionality rather than retrieval of specific organizations.

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 (searching organizations in cancer clinical trials) and includes practical constraints (API key requirement, city+state pairing). However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the many sibling tools.

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