Skip to main content
Glama
musharna

plant-genomics-mcp

blast_sequence

Performs BLAST sequence-similarity searches against NCBI databases, submitting queries and polling for results to return top hits.

Instructions

Run a BLAST sequence-similarity search against NCBI BLAST URLAPI. Async Put/Get under the hood — submits the query, polls the RID (honoring NCBI's per-RID 60s floor), and returns the parsed top hits + raw text report excerpt. Programs: blastn / blastp / blastx / tblastn / tblastx. Database defaults to swissprot for protein programs, core_nt for nucleotide. Emits notifications/progress on each poll. Long searches (>10 min) raise [NotFoundError] with the RID preserved so the client can re-poll. Set PLANT_GENOMICS_MCP_NCBI_EMAIL to identify the request per NCBI etiquette.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequenceYesRaw or FASTA-formatted query sequence.
programNoBLAST program — default blastp.blastp
databaseNoNCBI BLAST database slug (e.g. swissprot, core_nt, refseq_protein). Defaults to swissprot for protein programs and core_nt for nucleotide programs.
hitlist_sizeNoMax hits to return (default 10).
expectNoE-value threshold (default 10).
megablastNoEnable megablast (blastn only). Default false.
poll_intervalNoSeconds between polls. Clamped up to NCBI's per-RID 60s floor.
max_waitNoMax seconds to wait for the search to finish before raising NotFoundError with the RID preserved (default 600).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ridYesNCBI BLAST request ID — re-usable via fetch_result()
programYesblastn | blastp | blastx | tblastn | tblastx
databaseYesNCBI BLAST database, e.g. swissprot, core_nt
statusYesAlways "READY" when this object is returned
hitCountYesNumber of rows parsed from the alignment summary
hitsYesTop alignments, sorted by BLAST default order
raw_report_excerptYesFirst 50 KB of the FORMAT_TYPE=Text report
raw_report_truncatedYesTrue if the upstream report exceeded the cap
elapsed_secondsYesWall-clock from submit to READY
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It thoroughly discloses the async Put/Get mechanism, polling with per-RID 60s floor, notification/progress emission, error behavior (NotFoundError with RID preserved for long searches), default database selection by program type, and the email requirement. This covers all critical behavioral traits.

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 concise (6 sentences) and well-structured. It front-loads the core purpose and key behaviors, then details programs, databases, notifications, error handling, and prerequisite. Every sentence adds essential information without redundancy.

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 complexity (8 parameters, async external API, error handling) and that an output schema exists (though not shown), the description covers all necessary aspects: purpose, async flow, defaults, constraints, errors, and prerequisites. It is sufficient for an agent to invoke the tool correctly.

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 value beyond the schema: it explains the async flow, default database logic, constraint that megablast only works with blastn, poll_interval clamping, and max_wait timeout behavior. It also clarifies the output nature (top hits + raw excerpt). This far exceeds the baseline.

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 runs a BLAST sequence-similarity search against NCBI BLAST URLAPI. It specifies the verb (run BLAST), resource (NCBI BLAST URLAPI), and distinguishes from sibling tools which are plant-specific (e.g., analyze_locus_synth, bar_*). The description also lists supported programs and databases, making the tool's scope unambiguous.

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 provides context for when to use the tool (general BLAST search) and mentions a prerequisite (setting PLANT_GENOMICS_MCP_NCBI_EMAIL for NCBI etiquette). However, it does not explicitly state when not to use this tool or suggest alternatives among siblings, which would be straightforward given the siblings are plant-centric.

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