Skip to main content
Glama

blast_sequence

Read-onlyIdempotent

BLAST a DNA or protein sequence (raw or FASTA; up to 20 kb DNA or 5,000 aa) against this site's databases: B. napus Darmor-bzh v4.1 and ZS11, B. oleracea TO1000 and B. rapa Chiifu genomes; CDS and proteins of the three Ensembl genomes. The program is chosen from the query and database types (blastn, or blastn-short under 50 nt; blastx; blastp; tblastn against CDS only). databases: ids from the list this tool returns (default: DNA query -> reference genome + all CDS sets; protein -> all protein sets). Hits give gene ID (CDS/protein) or genome position with overlapping genes, identity, alignment length, e-value and a genome browser link. People can use the SequenceServer page at /blast/ for the same databases.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sequence": "<sequence>"
    },
    "name": "blast_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
evalueNo
max_hitsNo
sequenceYes
databasesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / databases / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds substantial context on top: input ceilings (20 kb DNA, 5,000 aa), program auto-selection rules, and how the databases argument must be sourced from this tool's own list. It also discloses the return contents (gene ID or genome position with overlapping genes, identity, alignment length, e-value, browser link), which matters because there is no output schema.

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?

Dense and front-loaded: the action, input limits, and database list lead, with selection logic and return format following. A few clauses are packed into long run-on sentences with semicolons, which slightly hurts scannability.

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

Completeness4/5

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

Given no output schema, the description does the work of explaining what hits contain, and it fully scopes the input and database behavior. The remaining gap is the two undocumented tuning parameters (evalue, max_hits), which an agent cannot reason about from the definition alone.

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 0%, so the description must carry all four parameters. It documents `sequence` (raw or FASTA, size caps) and `databases` (how to obtain ids, per-query-type defaults) well, but never mentions `evalue` or `max_hits`, leaving half the parameters with no semantics anywhere.

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?

States a specific verb (BLAST) and resource (DNA or protein sequence) plus the exact database scope, accepted input formats, and size limits. It is unmistakable from the sibling list, which contains no other BLAST/search-by-alignment 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?

Explains the internal decision logic clearly: the program is auto-selected from query and database type (blastn, blastn-short under 50 nt, blastx, blastp, tblastn only against CDS), and gives default database sets per query type. It stops short of naming sibling alternatives or saying when a different tool (e.g. find_gene, genes_in_region) is preferable.

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