Skip to main content
Glama

Hgnc

by io.github.pipeworx-io

Search Genes

search_genes
Read-onlyIdempotent

Fuzzy search across approved symbols, names, and aliases — e.g. "breast cancer", "p53", "tumor protein". Returns lightweight matches (hgnc_id, symbol, relevance score) ranked by score; call get_gene with a returned symbol for the full record. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax matches to return (default 10, max 25).
queryYesGene symbol, name fragment, or alias, e.g. "breast cancer", "p53", "kinase".

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare safe, idempotent, read-only behavior. Description adds that it returns lightweight matches ranked by score and is keyless, providing useful 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?

Two efficient sentences with no wasted words. Front-loaded with purpose and examples.

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?

No output schema, but description explains return fields (hgnc_id, symbol, relevance score) and ranking. Sufficient for a search tool with rich annotations.

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 already covers both parameters with descriptions (100% coverage). Description reinforces with examples (e.g., 'breast cancer', 'p53'), adding practical value 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?

Description clearly specifies fuzzy search across symbols, names, and aliases with concrete examples. Effectively distinguishes from sibling 'get_gene' which retrieves full records.

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?

Explicitly directs users to call get_gene for full records after searching. Implies this tool is for quick lightweight lookups; could add when not to use (e.g., when exact ID is known).

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Tools are mostly distinct but several ask_pipeworx variants and research tools overlap in purpose, which could lead to agent confusion. The presence of memory and subscription tools adds unrelated functionality.

Naming Consistency2/5

Naming is inconsistent, mixing snake_case with varying verb patterns (ask, get, search, scan, etc.) and no clear convention. Some tools have descriptive phrases (e.g., generate_llms_txt) further breaking consistency.

Tool Count2/5

34 tools is excessive for a coherent server, covering too many disparate domains (genes, data queries, betting, memory) without clear focus. A gene server should have far fewer tools.

Completeness3/5

Gene-related tools are complete for basic queries (search, get, resolve), but the server's main purpose (HGNC) is overshadowed by many unrelated Pipeworx tools, creating a mismatch. The overall surface is broad but lacks domain focus.

Resources