Skip to main content
Glama

Get Study

get_study
Read-only

Fetches cBioPortal study metadata—licence, citation, cancer type, sample counts, assembly, and molecular profile IDs/types—for a given study ID without data matrices; unknown IDs return not_found.

Instructions

Get one cBioPortal study: licence, restricted flag, citation, pmid, import_date, cancer type, sample counts, assembly, the fenced description and its molecular profiles (IDs and types only; no data matrices). An unknown ID is not_found. Signature: get_study(study_id).

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": {
      "study_id": "<study_id>"
    },
    "name": "get_study"
  }
}

Input Schema

NameRequiredDescriptionDefault
study_idYescBioPortal study ID (from search_studies).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds real context by naming the not_found behavior for an unknown ID and by stating that molecular profiles carry IDs and types only, with no data matrices. That scope disclosure prevents an agent from assuming matrices come back. It stops short of saying whether the description field is truncated ('fenced'), which leaves a small ambiguity.

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 the verb and resource, then the returned fields, then the error case — a sensible ordering with no filler prose. The field list is dense but each item conveys real information. The redundant signature line is the only sentence 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?

No output schema exists, so the description carries the full burden of describing return values, and it does so comprehensively, including the notable exclusions. With one required, fully documented parameter and annotations covering safety, nothing an agent needs to call this correctly is missing.

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 the study_id parameter already documents its pattern, example, and provenance (from search_studies), so the baseline is 3. The trailing 'Signature: get_study(study_id)' merely restates the single required parameter without adding format or constraint detail beyond the schema.

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?

A specific verb and resource ('Get one cBioPortal study') followed by an explicit enumeration of the fields returned (licence, restricted flag, citation, pmid, import_date, cancer type, sample counts, assembly, description, molecular profiles). The parenthetical '(IDs and types only; no data matrices)' draws a hard scope boundary that separates it from data-fetching siblings like get_gene_mutations.

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

Usage Guidelines3/5

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

Usage is only implied by the shape of the tool: fetch exactly one study by ID, where the ID comes from search_studies (stated in the schema, not the description). The description never says when to prefer this over search_studies or the other get_* tools. The only explicit guidance is the failure mode ('An unknown ID is not_found'), which is helpful but is not when-to-use guidance.

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