Skip to main content
Glama

Search Studies

search_studies
Read-only

Search public cBioPortal cancer studies by keyword, OncoTree type, or both to retrieve study metadata, sample counts, licences, and pagination, with restricted studies excluded by default.

Instructions

Search public cBioPortal studies by keyword (ID, name, citation) and/or cancer_type (OncoTree code, subtypes included), largest first. Each row: study_id, name, licence, restricted, citation, pmid, import_date, cancer_type, sample counts and assembly. Restricted (NC/ND) studies are excluded unless include_restricted (restricted_excluded counts them). No filter lists all. Signature: search_studies(query=, cancer_type=, include_restricted=, response_mode=, limit=, offset=).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_studies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 20, max 100).
queryNoKeyword, e.g. 'pan-cancer atlas'.
offsetNoRows to skip; use the previous `next_offset`.
cancer_typeNoLowercase OncoTree code as cBioPortal uses it (luad, skcm, mel); subtypes are included. Find codes with list_cancer_types.
response_modeNominimal: id, name, licence, citation | compact (default): + cancer type, sample counts, assembly | standard: + URL | full: + fenced description.
include_restrictedNoOpt in to studies with non-commercial/no-derivatives terms (flagged).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing a real trap: restricted (NC/ND) studies are silently excluded unless include_restricted is set, with restricted_excluded counting them, and the sort order is fixed at largest-first. It also enumerates the returned row fields, so the agent knows what comes back without an output schema.

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?

Front-loaded with purpose, then return shape, then the restricted-studies caveat and the no-filter case, all information-dense. The trailing 'Signature:' sentence largely duplicates the input schema and is the one element that does not earn its place.

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 a six-parameter, all-optional search with no output schema, the description covers searchable fields, ordering, default exclusions, toggling via include_restricted, and the fields returned. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, and the description adds real meaning: query matches ID/name/citation specifically, cancer_type accepts OncoTree codes with subtypes included, and include_restricted governs the restricted-studies exclusion. response_mode, limit, and offset are only restated in the signature line rather than explained.

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 ('Search public cBioPortal studies') plus the searchable fields (ID, name, citation) and result ordering ('largest first'). It also clarifies the zero-filter case ('No filter lists all') and points to list_cancer_types for codes, so an agent can distinguish it from get_study and list_cancer_types without opening a schema.

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?

Clear usage context: filtering dimensions, the default exclusion of restricted studies, and the explicit 'No filter lists all' behavior make the when-to-call condition obvious. It routes to list_cancer_types for code discovery but never explicitly contrasts with get_study for single-study retrieval, so no exclusion is stated.

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