Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

BLAST: Sequence Search (NCBI)

blast_sequence
Read-only

Submit a DNA or protein sequence to search against NCBI databases using BLAST. Returns top hits and alignment details.

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
expectNoE-value threshold (default 10).
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.
max_waitNoMax seconds to wait for the search to finish before raising NotFoundError with the RID preserved (default 600).
sequenceYesRaw or FASTA-formatted query sequence.
megablastNoEnable megablast (blastn only). Default false.
hitlist_sizeNoMax hits to return (default 10).
poll_intervalNoSeconds between polls. Clamped up to NCBI's per-RID 60s floor.

Output Schema

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

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

Description adds significant behavioral details beyond annotations: async Put/Get, polling with 60s floor, progress notifications, long search error with RID preservation, email requirement. No contradiction with annotations.

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?

Every sentence adds value; no fluff. Front-loaded with main purpose. Length is appropriate for 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 complexity (async, polling, error handling, many parameters) and presence of output schema, description covers essential behavior, defaults, error case, and environmental setup. Complete enough.

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 covers 100% of parameters with descriptions. Description adds value by summarizing program/database defaults and explaining notable parameters like megablast and poll interval, but does not add fundamental new meaning.

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 it runs a BLAST sequence-similarity search against NCBI. Verb+resource is specific ('Run' + 'BLAST sequence-similarity search'). Distinguished from sibling tools as the only BLAST tool.

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?

Provides clear context for use (sequence similarity search) but does not explicitly state when not to use or mention alternatives. However, sibling tools are not BLAST-related, so implied.

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