Skip to main content
Glama
yeyuan98

BioMCP

by yeyuan98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gene_get

Read-only

Retrieve detailed gene information by entering an official HGNC symbol. Optionally enable smart alias resolution and choose sections like pathways, diseases, protein, and expression to get targeted data.

Instructions

Get detailed gene information by symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
smartNoWhen true, automatically resolves gene aliases and common names to the official HGNC symbol before lookup (e.g., "HER2" → "ERBB2"). Zero overhead when input is already a valid HGNC symbol.
symbolYesOfficial HGNC gene symbol (e.g., "BRAF", "TP53", "ERBB2"). Common aliases like "HER2" or "NEU" are NOT accepted unless smart=true is enabled.
sectionsNoSections to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true (safe read) and openWorldHint=true (variable results). Description adds no additional behavioral context such as error handling, rate limits, or data scope beyond 'detailed', offering minimal extra transparency.

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?

Five-word sentence is extremely concise but includes the core action and resource. Could elaborate slightly without losing efficiency, but overall well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no output schema, and complexity of gene data, the minimal description fails to convey the scope of information returned (e.g., sections, smart resolution) or any usage nuances. Incomplete for effective tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (75%), but description provides zero additional parameter-level explanation. It does not compensate for 'limit' lacking schema description, and adds no semantics beyond the symbol parameter documented in 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 states verb 'Get' and resource 'detailed gene information by symbol', distinguishing it from sibling tools like gene_search or gene_articles which serve different retrieval purposes.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs. alternatives (e.g., gene_search for partial matches, gene_articles for literature). No when-not or context provided.

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

Deploy Server

Other Tools