variation_spdi_to_rsids
Pack: ncbi-variation · Endpoint: https://gateway.pipeworx.io/ncbi-variation/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/variation_spdi_to_rsids for the schema, then POST the same URL with its arguments for the data.
Maps a SPDI genomic coordinate and alleles back to the dbSNP rsIDs, via NCBI Variation Services.
Tool description as the model sees it
Look up the dbSNP rsIDs that a SPDI allele maps to, via NCBI Variation Services. AUTHORITATIVE for the reverse direction — you have a genomic coordinate and alleles from a VCF or a pipeline and need the rsID other databases key on. SPDI is 0-BASED, unlike HGVS: “NC_000007.14:140753335:A:T” is the same variant as “NC_000007.14:g.140753336A>T”.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
spdi | string | yes | SPDI as seq_id:position:deleted:inserted, 0-based position. e.g. “NC_000007.14:140753335:A:T”. |
Example call
Arguments
{
"spdi": "NC_000007.14:140753335:A:T"
}
curl
curl -X POST https://gateway.pipeworx.io/ncbi-variation/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"variation_spdi_to_rsids","arguments":{"spdi":"NC_000007.14:140753335:A:T"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('variation_spdi_to_rsids', {
"spdi": "NC_000007.14:140753335:A:T"
});
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"ncbi-variation": {
"url": "https://gateway.pipeworx.io/ncbi-variation/mcp"
}
}
}
See Getting Started for client-specific install steps.