Synonyms of a Biomedical Identifier: All Known Names for a Preferred CURIE (Translator Name Resolver)
rencinameresolver/synonyms
Returns every name the Translator Name Resolver holds for one preferred biomedical identifier (a CURIE such as MONDO:0005015): the preferred name, all synonyms, Biolink types, taxa and the number of identifiers in the concept. An identifier the service does not hold comes back as an empty object under its key. Use a preferred identifier, as returned by the name lookup. Data from the NCATS Translator Name Resolver (RENCI), served by Eden Engine; not an official RENCI 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 $0.50.
Data source
Translator Name Resolver (RENCI)
Source: NCATS Translator Standards Reference Implementation team at RENCI (infores:sri-name-resolver), Name Resolver service, name-resolution-sri.renci.org. Served by Eden Engine; not an official RENCI 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: "rencinameresolver/synonyms" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "rencinameresolver/synonyms" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "rencinameresolver/synonyms", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "rencinameresolver/synonyms", 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": [
"curie"
],
"properties": {
"curie": {
"type": "string",
"pattern": "^[^\\s:]+:\\S+$",
"maxLength": 200,
"minLength": 3,
"description": "One preferred identifier as PREFIX:LOCAL, for example MONDO:0005015 or NCBIGene:1017. One per call."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"description": "One key, the identifier asked for, mapped to its names, or to an empty object when the service does not hold it.",
"additionalProperties": {
"type": "object",
"properties": {
"taxa": {
"type": "array",
"items": {
"type": "string"
}
},
"curie": {
"type": "string"
},
"names": {
"type": "array",
"items": {
"type": "string"
},
"description": "Every known name of the concept."
},
"types": {
"type": "array",
"items": {
"type": "string"
},
"description": "Biolink types, most specific first."
},
"preferred_name": {
"type": "string"
},
"shortest_name_length": {
"type": "integer"
},
"clique_identifier_count": {
"type": "integer"
}
},
"additionalProperties": true
}
}