`ena_results_types`

Pack: ena · Endpoint: https://gateway.pipeworx.io/ena/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/ena_results_types for the schema, then POST the same URL with its arguments for the data.

List every ENA result type you can search — with its live record count and last-updated date — and, for one named result type, every field you may query or return. This is the schema-discovery step for ena_search: ENA rejects an unknown or wrong-result-type field name outright, so reading the field list first is cheaper than guessing. Also useful on its own for “how much public sequence data exists right now” — the counts are the archive’s live totals.

Parameters

Name	Type	Required	Description
`result`	string	no	Optional result type (e.g. read_run, study, sample) to also list its searchable/returnable fields. Omit to list result types only.

Example call

Arguments

{
  "result": "read_run"
}

curl

curl -X POST https://gateway.pipeworx.io/ena/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ena_results_types","arguments":{"result":"read_run"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('ena_results_types', {
  "result": "read_run"
});

More examples

{}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "ena": {
      "url": "https://gateway.pipeworx.io/ena/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

ena_results_types