Skip to main content
Glama

Find GenCC Curations

find_curations
Read-onlyIdempotent

Filter aggregated gene-disease validity assertions by classification, submitter, inheritance mode, gene, disease, or conflict status, with pagination. Retrieve harmonized GenCC data for targeted curation needs.

Instructions

Filter aggregated gene-disease assertions by classification(s), submitter(s), mode of inheritance, gene, disease, or conflict status, with limit/offset paging. Example: classification=['Definitive'], moi='Autosomal dominant', submitter=['ClinGen']. With NO filters it browses the whole catalog one page at a time (default 50 rows). classification/submitter/moi match at the submission level (any submitter), not the consensus -- each row's matched field names the triggering submission. Filter values are validated (case-insensitive); out-of-vocabulary values return invalid_input with the accepted set (case-insensitive; see get_server_capabilities / list_submitters), and an unresolvable gene or disease returns not_found. A filter passed as a blank string / empty list is rejected -- omit a filter to browse. Pass ids_only=true to return only {gene_curie, disease_curie} pairs for cheap paging. Large sweeps: follow truncated.next_cursor (an opaque, release-bound page token) via _meta.next_commands; a cursor minted under a prior data release is rejected so a weekly refresh can't silently skip or duplicate rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moiNoRestrict to one mode-of-inheritance title (closed vocabulary; case-insensitive; see get_server_capabilities.inheritance_modes).
limitNoRows per page (1-200; values above 200 are clamped).
cursorNoOpaque, release-bound page token from a prior truncated.next_cursor.
offsetNoZero-based row offset for paging.
diseaseNoRestrict to one disease (MONDO/OMIM CURIE or exact title); unresolvable -> not_found.
ids_onlyNoReturn only {gene_curie, disease_curie} pairs for cheap paging.
submitterNoRestrict to these submitters by title (e.g. ClinGen) or GenCC submitter CURIE; validated case-insensitively against the live roster (see list_submitters).
gene_symbolNoRestrict to one gene (approved symbol or HGNC CURIE); unresolvable -> not_found.
has_conflictNoKeep only pairs with (true) or without (false) a submitter conflict.
response_modeNoVerbosity: minimal | compact | standard | full.compact
classificationNoRestrict to submissions carrying one of these GenCC classification titles (closed vocabulary; case-insensitive).
Behavior5/5

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

The description goes well beyond the read-only/idempotent annotations by disclosing specific behaviors: out-of-vocabulary values return invalid_input with the accepted set, unresolvable genes/diseases return not_found, blank filters are rejected, and cursor semantics are documented (release-bound, rejected from prior releases). It also explains submission-level matching and the matched field, adding substantial context.

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 dense and front-loaded, starting with the main purpose and an example. Some information, such as ids_only's purpose, is repeated from the schema, and the cursor explanation is lengthy—but given the tool's complexity and the absence of an output schema, the length is justified. It earns a 4 rather than 5 due to minor redundancy.

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?

Despite lacking an output schema, the description documents key response elements (truncated.next_cursor, _meta.next_commands, matched field) and error semantics (invalid_input, not_found). It also covers edge cases like blank filters and cursor invalidation across releases, making it comprehensive for an 11-parameter read-only tool.

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?

The schema already covers 100% of parameters with descriptions, so the description's extra value comes from clarifying usage semantics: classification/submitter/moi match at submission level, ids_only for cheap paging, and cursor/offset paging behavior. These details are not in the schema descriptions, but the schema does the heavy lifting, so a 4 is appropriate.

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 opens with a specific verb and resource: "Filter aggregated gene-disease assertions by..." listing all filter dimensions. It also clarifies the no-filters browsing mode, distinguishing it from sibling tools like get_gene_curations which target a single gene or disease.

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 context is given that this tool browses the whole catalog and supports broad filtering, and it explicitly points to get_server_capabilities/list_submitters for accepted vocabularies. However, it never explicitly contrasts with alternative tools or states when not to use this one, so it falls short of a 5.

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

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/berntpopp/gencc-link'

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