gencc-link

Overview Schema Source Related Servers Discussions Admin

Search GenCC Genes

search_genes

Read-onlyIdempotent

Search the GenCC gene catalog by symbol, partial symbol, or HGNC ID to get ranked genes with assertion roll-ups, disease counts, and conflict flags. Resolve free text before fetching detailed curations.

Instructions

Search the GenCC gene catalog by approved symbol, partial symbol, or HGNC id. Returns ranked genes with assertion roll-ups (number of diseases, submitters, strongest classification, conflict flag). Use to resolve free text before get_gene_curations. Page large result sets via the release-bound truncated.next_cursor (surfaced as _meta.next_commands[0]).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Rows per page (1-200; above 200 is clamped).
`query`	Yes	Gene symbol, partial symbol, or HGNC id to search for.
`cursor`	No	Opaque, release-bound page token from a prior truncated.next_cursor.
`offset`	No	Zero-based row offset for paging.
`response_mode`	No	Verbosity: minimal \| compact \| standard \| full.	compact

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.8.2Jul 31, 2026

addedInput schema / properties / cursor / description

Added value: +"Opaque, release-bound page token from a prior truncated.next_cursor."

addedInput schema / properties / limit / description

Added value: +"Rows per page (1-200; above 200 is clamped)."

addedInput schema / properties / limit / examples
```
Added value: +[
+  20
+]
```
addedInput schema / properties / offset / description
```
Added value: +"Zero-based row offset for paging."
```
addedInput schema / properties / offset / examples
```
Added value: +[
+  0
+]
```
removedInput schema / properties / query / default
```
Removed value: -""
```

addedInput schema / properties / query / description

Added value: +"Gene symbol, partial symbol, or HGNC id to search for."

addedInput schema / properties / query / examples
```
Added value: +[
+  "BRCA1",
+  "SKI"
+]
```

changedInput schema / properties / response_mode / description

Previous value: -"Verbosity: minimal | compact | standard | full (default compact)."New value: +"Verbosity: minimal | compact | standard | full."

addedInput schema / properties / response_mode / examples
```
Added value: +[
+  "compact"
+]
```
addedInput schema / required
```
Added value: +[
+  "query"
+]
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "properties": {
-    "_meta": {
-      "additionalProperties": true,
-      "description": "Per-call envelope metadata.",
-      "properties": {
-        "citation_ref": {
-          "type": "string"
-        },
-        "citation_short": {
-          "type": "string"
-        },
-        "data_license": {
-          "type": "string"
-        },
-        "elapsed_ms": {
-          "type": "number"
-        },
-        "gencc_release": {
-          "type": "string"
-        },
-        "next_commands": {
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "arguments": {
-                "additionalProperties": true,
-                "type": "object"
-              },
-              "tool": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "tool",
-              "arguments"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "recommended_citation": {
-          "type": "string"
-        },
-        "request_id": {
-          "type": "string"
-        },
-        "response_mode": {
-          "type": "string"
-        },
-        "tool": {
-          "type": "string"
-        },
-        "unsafe_for_clinical_use": {
-          "type": "boolean"
-        }
-      },
-      "type": "object"
-    },
-    "count": {
-      "type": "integer"
-    },
-    "error_code": {
-      "type": "string"
-    },
-    "field_errors": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "genes": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "headline": {
-      "type": "string"
-    },
-    "message": {
-      "type": "string"
-    },
-    "query": {
-      "type": "string"
-    },
-    "recovery_action": {
-      "type": "string"
-    },
-    "retryable": {
-      "type": "boolean"
-    },
-    "success": {
-      "type": "boolean"
-    },
-    "total": {
-      "type": "integer"
-    },
-    "truncated": {
-      "additionalProperties": true,
-      "properties": {
-        "hint": {
-          "type": "string"
-        },
-        "next_cursor": {
-          "type": "string"
-        },
-        "next_offset": {
-          "type": "integer"
-        },
-        "returned": {
-          "type": "integer"
-        },
-        "total": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "required": [
-    "success"
-  ],
-  "type": "object"
-}New value: +null

First observedv0.5.3Jul 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds useful behavioral context about pagination (release-bound truncated.next_cursor surfaced via _meta.next_commands[0]) and the nature of results (ranked with assertion roll-ups), going beyond the annotations without contradicting them.

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?

Two sentences, front-loaded with the core purpose and return summary, followed by targeted usage guidance. No filler or redundancy; every sentence contributes actionable information.

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?

With no output schema, the description covers the key return fields (diseases, submitters, strongest classification, conflict flag) and provides pagination guidance. It might hint at response_mode effects or offset/cursor interplay, but overall it adequately frames the tool for a five-parameter search operation.

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 parameters are already documented. The description adds value by specifying how to use the cursor ('release-bound truncated.next_cursor surfaced as _meta.next_commands[0]') and clarifies query semantics (approved symbol, partial symbol, or HGNC id), which partially complements 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?

The description opens with a specific verb and resource: 'Search the GenCC gene catalog by approved symbol, partial symbol, or HGNC id.' It clearly states what the tool does, what it returns ('ranked genes with assertion roll-ups'), and distinguishes itself from siblings by positioning it as a free-text resolver before get_gene_curations.

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 explicitly says 'Use to resolve free text before get_gene_curations,' giving a clear when-to-use and an alternative. However, it doesn't explicitly state when not to use it (e.g., when a gene ID is already known), so it lacks full exclusions.

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

Install Server

Search GenCC Genes

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools