Skip to main content
Glama

get_sequence

Retrieve nucleotide or protein sequence information from NMDC by accession ID to look up sequence records using a known accession.

Instructions

Get sequence information (nucleotide or protein) from NMDC by accession ID.

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": {
      "accession": "<accession>"
    },
    "name": "get_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessionYesSequence accession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it establishes that this is a retrieval of stored sequence records and that the record may be nucleotide or protein. However, it says nothing about behavior on an unknown accession, whether partial or full records are returned, or whether authentication/rate limits apply.

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?

A single front-loaded sentence with no filler or redundant restatement of the title.

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?

For a one-parameter lookup with no output schema and no annotations, the description covers the essentials of what is fetched but leaves open what a result actually contains (raw sequence versus metadata) and how failures are signaled.

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?

With a single required parameter and 100% schema description coverage, the schema already defines 'accession' as a sequence accession ID. The description adds only the implied constraint that the ID must be valid for NMDC, with no format or example detail beyond the schema.

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?

The description gives a specific verb and resource ('Get sequence information'), names the source (NMDC), the data domain (nucleotide or protein), and the selector (accession ID). It is clearly distinguishable from the sibling search_* tools by being an ID-based lookup, though it never says so explicitly.

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?

There is no when-to-use guidance and no mention of alternatives, such as using the search_* siblings to discover an accession before calling this. The only implied guidance is that a known accession ID is required, which comes from the required parameter rather than from the description.

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