Skip to main content
Glama

search_sra

Search NMDC's Sequence Read Archive for raw sequencing data by keyword, with pagination to browse results.

Instructions

Search the Sequence Read Archive (SRA) data on NMDC. SRA stores raw sequencing data from various platforms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_sra"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordNoSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says nothing about read-only semantics, expected result shape, pagination behavior, or whether searches are exact-match or fuzzy, leaving the agent to infer all of this from the schema alone.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence is marginal but does add scope information about what the archive contains, so it earns partial credit rather than being pure waste.

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 simple three-parameter, zero-required search tool with fully documented parameters and no output schema, the description covers the essentials of what is searched. It is still thin on what a result looks like and how keyword matching works, which an agent would need to form a good query.

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 page, size, and keyword each documented in the schema including defaults and bounds. The description adds no additional meaning about keyword matching semantics (substring vs full-text, multiple terms, field targeting), so the baseline of 3 applies.

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 ("Search") and resource ("Sequence Read Archive (SRA) data on NMDC") and expands the acronym, so an agent knows exactly what is being queried. It does not, however, distinguish this from siblings such as search_nmdc_data or search_metagenome, which could also plausibly return sequencing records.

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

Usage Guidelines3/5

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

"SRA stores raw sequencing data from various platforms" implies the tool is for raw sequencing reads rather than derived or curated data, which gives a soft when-to-use signal. There is no explicit guidance on when to prefer this over sibling search tools, nor any stated exclusions or prerequisites.

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