Find Conversion Routes Between Two Life-Science Databases (TogoID)
togoid/find-routes
All the dataset paths that link a source database to a destination database in TogoID, up to a number of hops (1 to 4, default 3): each route is a list of dataset names you can give to the TogoID id-conversion tool. For example ncbigene to pdb gives routes through uniprot, go and ensembl_gene. Dataset names are lower-case keys such as ncbigene, uniprot, pdb. Two names with no connection, or an unknown name, return an empty list. TogoID data, passed through unmodified and served by Eden Engine; not an official TogoID product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.
Data source
Identifier mappings from TogoID, run by the Database Center for Life Science (DBCLS), Japan; link data and configuration at github.com/dbcls/togoid-config (MIT licence). Passed through unmodified. Served by Eden Engine; not an official TogoID product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "togoid/find-routes" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "togoid/find-routes" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "togoid/find-routes", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "togoid/find-routes", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 21, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"source",
"destination"
],
"properties": {
"source": {
"type": "string",
"pattern": "^[a-z0-9_]{2,60}$",
"description": "The source dataset name, lower case, for example ncbigene."
},
"max_hops": {
"type": "integer",
"default": 3,
"maximum": 4,
"minimum": 1,
"description": "Longest route to look for, in steps between datasets, 1 to 4. Default 3. Longer searches return many more routes."
},
"destination": {
"type": "string",
"pattern": "^[a-z0-9_]{2,60}$",
"description": "The destination dataset name, lower case, for example pdb."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"results"
],
"properties": {
"results": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": "string"
}
},
"description": "The list the service returns (a bare JSON array arrives as `results`)."
}
},
"description": "Each entry of `results` is one route: the ordered dataset names from source to destination.",
"additionalProperties": true
}