Skip to main content
Glama
Sign In

Hgnc

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Gene

get_gene
Read-onlyIdempotent

Exact lookup of an approved human gene by its official HGNC symbol — returns the full authoritative record: approved name, locus type, chromosomal location, alias/previous symbols, gene groups, and cross-references (Entrez, Ensembl, UniProt, OMIM, RefSeq, UCSC, CCDS). Use search_genes first if you only have a name fragment or aren't sure of the exact symbol. Keyless.

Input Schema

NameRequiredDescriptionDefault
symbolYesOfficial HGNC gene symbol, e.g. "BRCA1", "TP53", "EGFR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "symbol": "BRCA1"
+  },
+  {
+    "symbol": "TP53"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive nature. The description adds marginal value by listing return fields and indicating 'Keyless', but does not elaborate on behavioral nuances beyond what annotations provide.

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 a single sentence that efficiently conveys purpose and return data. It is slightly lengthy due to enumeration of fields, but not verbose. Information is front-loaded.

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 the tool's simplicity (one parameter, no output schema, and thorough annotations), the description is fully adequate. It provides all necessary context for an agent to select and invoke the tool correctly.

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?

The input schema already describes the single parameter with examples and coverage at 100%. The description confirms the parameter's purpose but adds no additional semantic value 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?

The description clearly states the tool performs an exact lookup of a human gene by its official HGNC symbol, specifying what is returned. It distinguishes itself from the sibling tool search_genes by emphasizing exact lookup vs. fragment search.

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

Usage Guidelines5/5

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

The description explicitly instructs to use search_genes first when unsure of the exact symbol or when having only a name fragment. This provides clear guidance on when to use this tool versus an alternative.

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

All Hgnc toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources