Skip to main content
Glama

Jean — Molecular Biology & Genomics

blast_search

Read-only

Search a sequence against NCBI BLAST+ at EMBL-EBI (blastn, blastp, blastx, tblastn or tblastx) over ENA, UniProtKB, PDB and the vector-screening sets.

Input Schema

NameRequiredDescriptionDefault
emailNoEBI requires a contact address on every submission (their abuse contact, not a login). Left empty, the one saved in any EMBL-EBI panel is used.
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
regionNowhich part of the open record to search, when no sequence is wired in. Values: whole (the whole record), selection (the current selection), feature (a named feature).whole
featureNothe feature's name, matched case-insensitively on the open record. Only applies when region is feature.
programNowhich BLAST program. The QUERY alphabet is derived from it and never asked for: blastx takes DNA and searches protein, tblastn the reverse. Values: blastn (blastn · dna query), blastp (blastp · protein query), blastx (blastx · dna query), tblastn (tblastn · protein query), tblastx (tblastx · dna query).blastn
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.
sequenceNothe query. Wire a record or a sequence output, or paste raw/FASTA. Left empty, the region below is taken from the open record.
databasesNodatabase ids to search, as the service names them (em_rel, uniprotkb, pdb, emvec…). Several are searched together. Left empty, the service's OWN default for this program's context is used and reported back.
parametersNoevery other advertised parameter, one `id=value` per line, using the service's own ids (exp, matrix, filter, gapopen, gapext, wordsize, alignments, scores, taxids…). Left empty each keeps the service's default for this context. An id the service does not advertise is refused by name rather than dropped.

Output Schema

NameRequiredDescriptionDefault
hitsYesevery hit, with its HSPs, accession, organism and the links the service sent
jobIdYesthe dispatcher job id: what a methods section cites and what re-fetches this exact result
topHitYesthe best hit by E-value: what a "what is this?" step reads
tabularYesthe hits as BLAST's own outfmt 6 table, for download or a downstream parser
hitCountYeshow many subjects matched
sequencesYesthe hit subjects as FASTA, ready to wire straight into an alignment or a tree
topExpectYesthe best hit's E-value; wire into a $when to branch on significance
provenanceYesthe binary, the command line EBI ran, the databases as built, and the search space the E-values are relative to
topCoverageYeswhat fraction of the query the best hit covers, 0–1
topIdentityYespercent identity of the best hit's best HSP

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / topIdentity / x-unit
      Added value: +"%"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds that the search is remote (hosted at EMBL-EBI) against external reference databases. It says nothing about the behavior that actually matters for a remote BLAST submission: whether the job is synchronous or queued, expected latency, size of result payload, or what happens on service failure. Useful but not rich beyond the annotations.

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?

A single front-loaded sentence with no filler; the program list and database coverage are stated immediately. The parenthetical program enumeration partly duplicates the schema enum, which is mild redundancy but justifies its place as an at-a-glance capability summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the nine parameters including the nested _subject object are fully documented in the schema. What remains missing for a nine-parameter open-world remote search is operational context — submission/queue behavior, expected turnaround, and when to prefer a local or project-scoped BLAST sibling.

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 description coverage is 100%, with detailed per-parameter prose for program, region, feature, databases, sequence, _subject and parameters, so the baseline is 3. The description text itself adds no parameter meaning beyond restating which programs and database families exist, which the enums and descriptions already carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search a sequence against NCBI BLAST+ at EMBL-EBI'), enumerates the five supported programs and the target database families (ENA, UniProtKB, PDB, vector screening). What it does is unambiguous, but it never contrasts itself with nearby siblings such as blast_project_sequences, delta_blast_smart, rps_blast_cdd or ebi_align, so an agent must guess which BLAST wrapper is the right one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description sentence contains no when-to-use, when-not-to-use, or alternative-tool guidance at all. Routing hints exist only inside the schema (e.g. empty sequence falls back to the open record's region), which is not the description's job here. With ten-plus BLAST/alignment siblings in the catalog, the absence of selection guidance is a real gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources