Skip to main content
Glama
musharna

plant-genomics-mcp

kegg_pathways

Fetch KEGG pathway memberships for an Arabidopsis locus. Returns pathway IDs, names, and category classes.

Instructions

Fetch KEGG pathway memberships for an Arabidopsis locus from rest.kegg.jp. Returns a list of pathway IDs + names + KEGG category classes the locus participates in. Pairs with locus_go_annotations for the GO-level functional view. Multi-organism caveat (v1.1.0): the organism= field accepts any plant in the matrix for symmetry with the other backends, but only arabidopsis_thaliana resolves — KEGG uses NCBI Entrez Gene IDs for rice/maize/etc. and our cross-backend locus contract can't produce those yet, so any other organism raises OrganismNotSupported before any HTTP call. KEGG v118+ is case-sensitive on the locus: pass AGI loci as uppercase.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYesArabidopsis AGI locus, e.g. AT1G01010 (case preserved verbatim — KEGG v118+ is case-sensitive)
organismNoPlant organism — only arabidopsis_thaliana is supported in v1.1.0; other plants raise OrganismNotSupported until an Entrez bridge landsarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYes
organismYesResolved canonical organism slug, e.g. arabidopsis_thaliana
kegg_gene_idYese.g. "ath:at1g01010"
entrez_gene_idNoEntrez Gene ID from the non-Arabidopsis KEGG↔Entrez bridge; absent for ath.
pathwaysYes
errorsNoPer-pathway step-2 failures (kept inline so the call doesn't abort)
Behavior4/5

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

With no annotations, the description covers the source (rest.kegg.jp), return type, limitation on organism (unsupported ones raise error), and case-sensitivity. It does not mention pagination or rate limits but is fairly transparent for this tool.

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?

The description is structured with a clear first sentence for purpose, then pairing info and caveats. It is slightly verbose but each sentence contributes useful information; could be slightly more concise but still effective.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, output schema present), the description covers all key aspects: what it does, limitations, error conditions, and pairing with related tools. No gaps for an agent to miss.

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?

Both parameters have complete schema descriptions (100% coverage). The description adds extra context: case-sensitivity for locus and the organism limitation beyond what the schema provides, which enhances understanding.

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?

The description clearly states it fetches KEGG pathway memberships for an Arabidopsis locus and specifies the return format (list of pathway IDs, names, categories). It differentiates from sibling tool locus_go_annotations by indicating pairing with it for a different functional view.

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?

Provides context on when to use this tool (e.g., pairing with locus_go_annotations) and includes caveats about organism support and case-sensitivity, but does not explicitly contrast with other pathway-related siblings like batch_kegg_pathways.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musharna/plant-genomics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server