Skip to main content
Glama

Get Gene Group

get_gene_group
Read-onlyIdempotent

Retrieve a HGNC gene group or family by numeric ID or name. Returns member genes in symbol‑ordered summaries with pagination support.

Instructions

Browse a HGNC gene group/family by numeric group id (e.g. '1157') or by name (e.g. 'RAF family'). Returns the member genes as symbol-ordered summaries. Members are paginated with limit + offset; the response carries member_count, returned, truncated, and next_offset, and (when truncated) a next_commands entry that fetches the next page. A name matching several groups returns the candidate groups so you can re-call with a specific id. Signature: get_gene_group(group, limit=, offset=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesGene group id (numeric) or group name.
limitNoMax members (default 200).
offsetNoSkip this many members for pagination (default 0).
response_modeNoVerbosity: minimal | compact | standard | full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
_metaNo
fieldNo
limitNo
scoreNo
offsetNo
matchesNo
membersNo
messageNo
successNo
group_idNo
obsoleteNo
returnedNo
ambiguousNo
retryableNo
truncatedNo
candidatesNo
error_codeNo
group_nameNo
match_countNo
next_offsetNo
replaced_byNo
member_countNo
allowed_valuesNo
recovery_actionNo
Behavior4/5

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

Annotations already indicate safe read operation. Description adds pagination details (member_count, returned, truncated, next_commands) and name ambiguity resolution, providing behavioral context beyond annotations.

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?

Five sentences, each adding value: purpose, input format, output, pagination, ambiguous case, signature. Front-loaded and efficient.

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?

Given output schema availability, description adequately covers all aspects: parameters, pagination, edge cases (multiple groups), and response structure. No gaps.

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 covers 100% of parameters. Description adds examples for 'group', mentions pagination for limit/offset, and explains verbosity levels for response_mode, providing extra meaning beyond 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?

States clearly it browses a HGNC gene group/family by numeric id or name and returns member genes. Differentiates from sibling tools like get_gene (single gene) and search_genes.

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?

Specifies input formats (numeric id or name) and describes behavior when name matches multiple groups. Does not explicitly state when not to use, but pagination and candidate handling are clear.

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/hgnc-link'

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