Skip to main content
Glama
musharna

plant-genomics-mcp

string_interactions

Fetch protein-protein interaction partners from STRING-DB for plant species. Input a UniProt accession or locus identifier to retrieve first-neighbor interactions with combined and sub-scores.

Instructions

Fetch protein-protein interaction partners from STRING-DB (string-db.org). Accepts either a UniProt accession or a locus identifier — the latter is resolved via UniProt first. Defaults to arabidopsis_thaliana; pass organism= for other plant species (slug, scientific/common name, or NCBI taxid). Returns first-neighbor partners with the combined STRING score plus per-channel sub-scores (experimental, database, textmining, predicted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locus_or_accessionYesUniProt accession (Q0WV96) or locus (AT1G01010)
limitNoNumber of partners to return
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe locus or accession the user passed
accessionYesUniProt accession actually queried at STRING
organismYesPlant organism canonical slug, e.g. arabidopsis_thaliana
partnersYes
Behavior4/5

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

No annotations are provided, but the description discloses behavioral traits such as resolving locus identifiers via UniProt, defaulting to arabidopsis_thaliana, and returning first-neighbor partners with sub-scores, which adequately informs the agent.

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 concisely convey the main purpose, input variations, and output details without redundancy. The description is front-loaded and every sentence adds value.

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 presence of an output schema, the description thoroughly covers input parameters, default behavior, and output structure. No gaps remain for an agent to correctly invoke the tool.

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 description adds significant meaning beyond the schema by explaining that locus_or_accession accepts both accessions and loci, detailing organism parameter flexibility (slug, name, taxid), and clarifying the output structure.

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 fetches protein-protein interaction partners from STRING-DB, specifies input types (UniProt accession or locus identifier), and distinguishes itself from sibling tools like batch_string_interactions by indicating single-query usage.

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 when to use the tool (to fetch interaction partners) and how to specify organisms, but does not explicitly mention when to avoid it or suggest alternatives like the batch version for multiple queries.

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