Skip to main content
Glama

NCBI GenBank nucleotide record search: accession

health_genbank_nucleotide_seq
Read-only

NCBI GenBank nucleotide record search (nuccore): accession with version, title, sequence length, organism, molecule type and last update date. Metadata only, no sequence. Accepts an accession (e.g. NM_000546), a gene or any NCBI search term. Up to 10 records per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "term": "<term>"
    },
    "name": "health_genbank_nucleotide_seq"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many records, 1 to 10 (default 5)
termYesAccession or search term, letters, digits, spaces, brackets, dots, hyphens, 2 to 100 characters

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses the return scope (metadata only, no sequence), a result cap (up to 10 records per call), and the commercial behavior: $0.002 per successful call via x402 USDC on Base/Solana plus 10 networks, with failed calls not charged. Cost and payment mechanics are exactly the kind of behavioral context annotations cannot convey.

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?

Three tight sentences, front-loaded with what the tool returns, then input forms, then limits and cost. Nothing is redundant with the schema or annotations, and the pricing sentence, though long, carries information an agent must have before calling.

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?

An output schema exists, so return-value detail is unnecessary, and annotations cover the read-only/open-world profile. The description still supplies everything else an agent needs to call correctly: input forms, result cap, metadata-only scope, and billing consequences.

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 coverage is 100%, so the baseline is 3, but the description adds real semantic value: it shows a concrete accession form (NM_000546) and clarifies that 'term' also accepts gene names or arbitrary NCBI search expressions, which the schema's character-class description does not convey. It also restates the 10-record ceiling tied to the 'max' parameter.

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 and resource ('NCBI GenBank nucleotide record search (nuccore)') and enumerates exactly what each record contains: accession with version, title, sequence length, organism, molecule type, last update date. The 'Metadata only, no sequence' clause sharply distinguishes it from any sequence-retrieval expectation, so an agent knows precisely what it gets back.

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?

The description tells the agent what inputs are acceptable ('an accession (e.g. NM_000546), a gene or any NCBI search term'), which is concrete invocation guidance. It does not name when to prefer this over other health/genomics siblings (e.g. dbSNP, ClinVar) or state exclusions, so it falls short of explicit alternative routing.

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