Skip to main content
Glama

get_download_list

Retrieve a list of downloadable NMDC datasets and available bulk data downloads to identify microbiology data ready for download.

Instructions

Get the list of downloadable datasets from NMDC. Provides information about available bulk data downloads.

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": "get_download_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden; it does clarify this returns a listing of downloadable datasets rather than the bulk data itself, which is useful scoping. It says nothing about access requirements, whether downloads require authentication, pagination, or whether results are filtered — but for a zero-parameter read-only listing the risk is low, so a 3 fits.

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, front-loaded with the core action. The second sentence largely restates the first ("downloadable datasets" vs "bulk data downloads") and could be cut or replaced with more useful content.

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?

There is no output schema, so the description should indicate what the listing actually contains (dataset names, identifiers, download formats or URLs) and it does not. For a simple no-parameter list tool this is adequate to call correctly, but an agent cannot anticipate the shape of the result.

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?

The tool takes no parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description does not invent or misdescribe any inputs.

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?

States a specific verb and resource ("Get the list of downloadable datasets from NMDC") and names the originating repository, which lets an agent distinguish it from the metadata-oriented search_* siblings. It stops short of explicitly contrasting itself with those siblings, so it is clear but not maximally differentiated.

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 or when-not-to-use guidance and no alternative named. The second sentence ("Provides information about available bulk data downloads") restates the purpose rather than telling an agent when this tool is the right call versus search_nmdc_data or get_nmdc_data_overview.

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