Skip to main content
Glama
musharna

plant-genomics-mcp

locus_literature

Search Europe PMC for literature mentioning a plant locus, returning publication details including title, authors, journal, and abstract for up to 25 results.

Instructions

Search Europe PMC for literature mentioning a plant locus. Free, no API key. Returns up to size results (default 10, capped at 25) with title, authors, journal, year, DOI, PMID, open-access status, citation count, and abstract. For non-Arabidopsis species the species common name is appended to the query to disambiguate locus IDs (rice, maize, ...). Pair with resolve_locus_to_uniprot or ensembl_plants_lookup_locus to ground the locus before fanning out to the literature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYese.g. AT1G01010 (Arabidopsis), Os01g0100100 (rice)
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana
sizeNoMax results (1–25, default 10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYes
organismYes
queryYesFinal query string sent to Europe PMC
hitCountYesTotal hits available upstream (may exceed returned)
returnedYesNumber of hits actually in hits[]
hitsYes
Behavior4/5

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

With no annotations, the description discloses key behaviors: free, no API key, returns specific fields, appends species name for non-Arabidopsis, and caps results at 25. It provides adequate transparency beyond schema.

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?

Three sentences front-loaded with purpose, then output details, then pairing suggestions. Efficient and no wasted words.

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 there is an output schema, the description covers purpose, usage, parameters, and relationships to other tools. It is complete for the tool's function.

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?

Schema coverage is 100%, but the description adds value by explaining defaults and behavior (e.g., species disambiguation, size cap). It provides examples and context for locus and organism parameters.

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 the tool searches Europe PMC for literature mentioning a plant locus, with specific verb and resource. It distinguishes from siblings by mentioning pairing with resolve_locus_to_uniprot or ensembl_plants_lookup_locus.

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 notes it is free with no API key, suggests pairing with other tools, and explains species name appending for non-Arabidopsis. However, it lacks explicit when-not-to-use guidance among the many sibling tools.

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