Skip to main content
Glama

Mygene Info Query

mygene_info_query
Read-onlyIdempotent

Full-text gene query.

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": {
      "query": "BRCA1"
    },
    "name": "mygene_info_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo1-1000 (default 10).
sortNo
queryYese.g. "BRCA1", "symbol:TP53 AND taxid:9606"
fieldsNoComma-sep return fields.
speciesNoNCBI taxonomy id or common name (default human).

Output Schema

NameRequiredDescriptionDefault
hitsNoArray of gene matches
tookNoQuery execution time in milliseconds
totalNoTotal number of matching genes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

The annotations already declare this to be a safe, idempotent, open-world read operation, so the description need not restate safety. Beyond "full-text," it adds no behavioral context such as relevance ranking, query parsing behavior, result limits, or how full-text matching differs from the sibling gene tool.

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?

The description is a single front-loaded sentence with no wasted words. Its brevity is efficient but also under-specifies the tool's scope and routing value.

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?

For a five-parameter search tool with a sibling gene lookup, the definition is too thin even accounting for annotations and the output schema. It omits the full-text scope, result semantics, and when-to-use distinctions that an agent needs to select it 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?

Schema description coverage is 80%, so the schema already documents most parameters, including query examples and size bounds. The description adds no parameter meaning beyond that baseline.

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?

"Full-text gene query" gives a broad verb and resource, so the agent knows this searches genes. However, it does not distinguish this tool from siblings such as mygene_info_gene or clarify whether it searches all gene text or specific indexed fields.

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?

The description gives no when-to-use guidance, no exclusions, and no alternatives. An agent cannot tell from the definition when this full-text query should be preferred over mygene_info_gene or mygene_info_metadata.

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.