Skip to main content
Glama

Mygene Info Gene

mygene_info_gene
Read-onlyIdempotent

Annotations for a single gene id.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gene_id": "7157"
    },
    "name": "mygene_info_gene"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
gene_idYesEntrez id ("7157") or Ensembl id ("ENSG00000141510").
speciesNo

Output Schema

NameRequiredDescriptionDefault
_idNoGene ID
nameNoGene name
taxidNoNCBI taxonomy ID
symbolNoGene symbol
entrezgeneNoEntrez gene ID
descriptionNoGene description
ensemblgeneNoEnsembl gene ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing beyond them — no note about unknown-id behavior, whether results are cached, or that lookups hit an external service.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with zero padding, which is structurally clean, but the brevity comes from under-specification rather than disciplined editing — the sentence could easily carry parameter and usage detail.

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?

An output schema exists, so return values need not be described, but for a three-parameter tool with two undocumented parameters the description leaves the agent without enough to call it correctly or to distinguish it from the sibling query/metadata tools.

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 only 33%: gene_id is documented in the schema, but fields and species are bare strings. The description does not explain that fields selects which annotation categories are returned or that species disambiguates the lookup, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Annotations for a single gene id" names the resource (gene annotations) and the scope (a single id), which loosely distinguishes it from the sibling query tool. But it is a noun phrase without a specific verb, and it never says what kind of annotations (symbol, name, taxid, etc.) come back.

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?

There is no when-to-use guidance, no mention of when to prefer this over mygene_info_query or mygene_info_metadata, and no note about prerequisites such as needing an Entrez or Ensembl identifier.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.