Skip to main content
Glama
musharna

plant-genomics-mcp

blast_sequence

Run BLAST sequence-similarity searches against NCBI databases. Returns parsed top hits and raw report excerpt.

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?

Discloses async Put/Get polling, NCBI's 60-second floor, NotFoundError with preserved RID, progress notifications, and the required NCBI_EMAIL environment variable. Since annotations are absent, the description carries the full burden and exceeds it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Sentences are front-loaded with the core action and each adds value (async, programs, databases, errors, email). Slightly lengthy but efficient for the complexity.

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 (async, polling, NCBI constraints, multiple parameters), the description covers all essential aspects: action, data flow, error handling, and configuration. Output schema exists, so return format is already documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 8 parameters with 100% description coverage. The description provides no additional parameter specifics beyond what the schema already states, so baseline 3 applies.

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?

Clearly states the tool executes a BLAST sequence-similarity search against NCBI BLAST URLAPI. The verb 'Run' and resource are specific, and no sibling tool offers BLAST, making it distinct.

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?

Implies usage for sequence similarity searches by listing available programs and database defaults. Lacks explicit 'when not to use' or alternatives, but given no sibling BLAST tool, the context is sufficient.

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