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: Chinese Spring RefSeq v1.0 genome, RefSeq v1.1 CDS and proteins. 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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: input size ceilings (20 kb DNA / 5,000 aa), automatic program selection, default database resolution per query type, and the shape of hits (gene ID or genome position with overlapping genes, identity, alignment length, e-value, browser link). It does not say whether the search is synchronous or how long it takes, which is the main remaining transparency gap.

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?

Front-loaded with the verb, resource and size limits, then layered program selection, database defaults, and hit contents. Dense but every clause carries information; the only drag is the oddly wrapped parenthetical about program selection and the slightly confusing phrase 'ids from the list this tool returns'.

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?

With no output schema and no schema descriptions, the description does the heavy lifting well: input formats and limits, auto program choice, database defaults, and return fields are all covered. Missing only the semantics of evalue/max_hits and a clarification of which call returns the database list.

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 parameter meaning. It documents two of four: `sequence` (raw or FASTA, with length limits) and `databases` (IDs from the list this tool returns, with per-query-type defaults). It says nothing about `evalue` or `max_hits`, leaving the schema titles to convey those.

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/protein sequence) plus the target database set, and no sibling tool does similarity search, so it is unambiguously identifiable among the listed siblings.

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?

Gives concrete selection rules — program is auto-chosen from query and database types (blastn, blastn-short under 50 nt, blastx, blastp, tblastn against CDS only) and defaults differ for DNA vs protein queries — plus a pointer to the SequenceServer web page for the same data. It stops short of explicit when-not-to-use guidance, but there are no competing BLAST siblings to disambiguate against.

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