Skip to main content
Glama

Gtex

by io.github.pipeworx-io
OverviewAdmin

Gene

gene
Read-onlyIdempotent

Gene metadata by Gencode id or symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gencode_id_or_symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "gencode_id_or_symbol": "BRCA1"
+  },
+  {
+    "gencode_id_or_symbol": "ENSG00000012048.14"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Gene metadata response from GTEx API",
+  "type": "object"
+}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds no additional behavioral context, such as output format, pagination, or error handling. It relies entirely on 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?

The description is a single, concise sentence with no wasted words. It is appropriately sized for the tool's simplicity.

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?

Despite having an output schema, the description is too minimal. It does not explain what 'gene metadata' includes, whether multiple results are possible, or how to interpret the output. Additional context about the tool's scope would improve completeness.

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?

With 0% schema description coverage, the description must compensate but only says 'by Gencode id or symbol.' This implies the parameter accepts those identifiers but lacks format details, examples (though present in schema), or clarification that both types are accepted. The schema's examples partially fill the gap, but the description could be more explicit.

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

Purpose4/5

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

The description 'Gene metadata by Gencode id or symbol' clearly states the tool's purpose: retrieving gene metadata based on an identifier. It uses a specific verb-resource combination, but does not explicitly differentiate from similar tools like 'top_expressed_genes' or 'single_tissue_eqtls', which also involve genes.

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 is provided on when to use this tool versus alternatives. The description does not specify scenarios where querying by Gencode id vs symbol is appropriate, nor does it mention any prerequisites or limitations.

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

All Gtex 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.

Resources