plant-genomics-mcp

Overview Schema Source Related Servers Discussions Admin

Upstream Release

upstream_release

Read-onlyIdempotent

Check the current data release of a backend that does not pin releases on its answers. Read before and after a run; equal values mean no release changed in between.

Instructions

Report the release a backend's own release endpoint calls current, for the backends whose answers state none (their tools' upstream_version is always null). It is read by a SEPARATE request at query time, so it is not proof of the release that answered any one call: read it before and after a run, and equal values mean no release changed in between. Never cached. ensembl_plants: the Ensembl Genomes release (e.g. '63'); string: the STRING release ('12.0'); quickgo: the GO annotation load date and the GO ontology date; jaspar: the newest ACTIVE release (several are active at once); kegg: the pathway and genes last-update dates (KEGG has no release number). pdbe, aragwas and europe_pmc publish no data release: release is null and reason says why. Backends whose answers state or pin their release (UniProt, InterPro, PANTHER, AlphaFold, Gramene, ATTED-II, OrthoDB) are not listed: read upstream_version on their answers instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`backend`	Yes	The backend whose current release to read

Output Schema

TableJSON Schema

Name	Required	Description
`reason`	Yes	What the value is, or why there is none
`backend`	Yes	The backend asked about
`release`	Yes	The release its own endpoint calls current at query time — a DIFFERENT request from any data call, so not proof of the release that answered one. null when the backend publishes no data release (see reason)
`endpoints`	Yes	Full URLs of the release endpoints read, as provenance; [] when the backend publishes none — a link for the client to open or fetch; no tool on this server dereferences it
`components`	Yes	The release's parts by name, e.g. QuickGO annotation + go dates; {} when null
`observed_at`	Yes	UTC time the endpoints were read (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.27.0Sep 27, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare the tool read-only, open-world, idempotent, and non-destructive. The description adds significant behavioral context beyond those hints: the release is read by a separate request at query time, it is not proof of the release that answered any one call, and it is never cached. These disclosures meaningfully prevent misuse.

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 dense but every sentence earns its place: it states the core purpose, flags an important query-time caveat, lists backend-specific semantics compactly, and closes with an exclusion rule. The backend mapping is structured in a readable semicolon-separated list, avoiding unnecessary prose.

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 conceptual complexity—different meanings of 'release' per backend, null returns, and query-time semantics—the description is complete. It explains when to use this over reading upstream_version, warns about interpretation, and the output schema covers return structure, so nothing an agent needs to call it correctly is missing.

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% and the single parameter has an enum, but the description greatly enriches each enum value, explaining exactly what 'release' means per backend, e.g., STRING '12.0', quickgo's annotation and ontology dates, and kegg's last-update dates. It also clarifies that pdbe, aragwas, and europe_pmc return null with a reason because they publish no data release.

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 opens with a specific verb and resource: 'Report the release a backend's own release endpoint calls current.' It also explicitly distinguishes this tool from sibling tools by naming which backends are not listed and where to read their releases instead, so an agent can tell exactly what this tool covers.

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?

The description states clear when-to-use guidance: use this tool for backends whose answers state none and whose upstream_version is always null, and explicitly says when not to use it, directing the agent to read upstream_version on answers for UniProt, InterPro, PANTHER, AlphaFold, Gramene, ATTED-II, and OrthoDB. It also advises reading before and after a run to verify no release changed.

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

Deploy Server