Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

KEGG Pathways

kegg_pathways
Read-onlyIdempotent

Retrieve KEGG pathway annotations for an Arabidopsis gene locus, including pathway IDs, names, and categories.

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
errorsNoPer-pathway step-2 failures (kept inline so the call doesn't abort)
organismYesResolved canonical organism slug, e.g. arabidopsis_thaliana
pathwaysYes
kegg_gene_idYese.g. "ath:at1g01010"
entrez_gene_idNoEntrez Gene ID from the non-Arabidopsis KEGG↔Entrez bridge; absent for ath.
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds crucial behavioral context: case-sensitivity of KEGG v118+, the HTTP source (rest.kegg.jp), and the error behavior for unsupported organisms. No contradictions.

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 a single paragraph, front-loaded with purpose, but the multi-organism caveat is detailed. Each sentence adds value, but could be tightened slightly.

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?

For a tool with output schema, good annotations, and 2 parameters, the description covers limitations, usage context, and partner tools. It is complete.

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

Parameters5/5

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

Schema coverage is 100%, but description adds value: for 'locus', it stresses case-preservation and sensitivity; for 'organism', it explains the limitation and error. This goes beyond the schema's basic descriptions.

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 states a specific verb+resource ('Fetch KEGG pathway memberships for an Arabidopsis locus') and lists the return types (pathway IDs, names, categories). It distinguishes from siblings by mentioning pairing with locus_go_annotations and noting the organism limitation.

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

Usage Guidelines5/5

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

Explicitly states when to use (for pathway memberships), when not to (other organisms raise OrganismNotSupported), and suggests pairing with locus_go_annotations. The multi-organism caveat provides clear guidance.

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