Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

AlphaFold: Predicted Structure

alphafold_structure
Read-onlyIdempotent

Retrieve AlphaFold predicted structure summary for a plant gene locus. Returns confidence metrics, model version, and download links for 3D structure files.

Instructions

Fetch the AlphaFold DB predicted-structure summary for a locus (alphafold.ebi.ac.uk; free, no key). Resolves the locus → UniProt accession, then returns the predicted model's global mean pLDDT confidence, the per-band pLDDT distribution, modelled residue span, latest model version, and mmCIF / PDB / PAE download URLs. A valid protein with no deposited model returns found=false (a normal outcome, not an error); a locus with no UniProt entry raises a typed NotFoundError. Works for all 12 organisms (UniProt-keyed). Complements resolve_locus_to_uniprot (sequence-level) with the structure-level view. Defaults to arabidopsis_thaliana; pass organism= for other species.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYese.g. AT4G09760 (Arabidopsis), Os01g0100100 (rice RAP-DB)
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneNoGene name from UniProt
foundYesTrue if a predicted model exists
locusYes
cif_urlNommCIF model download URL
pdb_urlNoPDB model download URL
organismNoOrganism scientific name
accessionYesResolved UniProt accession
mean_plddtNoGlobal mean pLDDT confidence (0–100)
descriptionNoUniProt protein description
plddt_bandsNoFraction of residues per confidence band
model_createdNoModel creation date (ISO 8601)
pae_image_urlNoPredicted-aligned-error image URL
residue_rangeNoModelled residue span {start, end}
latest_versionNoLatest AlphaFold model version
model_entity_idNoe.g. AF-Q9SZ92-F1
Behavior5/5

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

Annotations indicate readOnly, idempotent, non-destructive, and open-world. The description adds: external database access (alphafold.ebi.ac.uk), free no key requirement, and specific error handling (found=false vs NotFoundError). 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.

Conciseness5/5

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

The description is approximately 100 words, front-loaded with the main action, and each sentence adds value. No redundant or vague statements.

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 output schema exists, the description covers all necessary aspects: source, free usage, workflow, edge cases, default organism, and sibling relation. It is complete and informative.

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%, baseline 3. The description adds concrete examples for locus (AT4G09760, Os01g0100100) and explains organism accepts slugs, names, or taxids. This provides significant extra meaning beyond the schema.

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 the AlphaFold DB predicted-structure summary for a locus, specifying the source and that it's free. It distinguishes from the sibling tool resolve_locus_to_uniprot by noting it provides the structure-level view, complementing the sequence-level 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?

The description explains the workflow (resolves locus to UniProt, returns specific data), handles edge cases (found=false for missing model, NotFoundError for invalid locus), and states the default organism. It mentions the sibling tool relation, but lacks explicit 'use this when' 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