Skip to content
Eden Engine
Get started

TogoID Dataset Description: Label, Category and Identifier Pattern

togoid/dataset-info

The description of one TogoID dataset by its lower-case key (for example ncbigene, uniprot, chembl_compound): its label, category, the regular expression its identifiers follow, example identifiers, the URI prefixes and links used to resolve them and the annotation fields it carries. An unknown key is refused as a validation error. TogoID data, passed through unmodified and served by Eden Engine; not an official TogoID product.

activeper callv1

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

DBCLS TogoID

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.

Install itCreate an account
agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "togoid/dataset-info" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "togoid/dataset-info" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "togoid/dataset-info", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "togoid/dataset-info", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not 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.

ChargePrice
Per call
$0.0026
Updated
Oct 21, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "required": [
    "dataset"
  ],
  "properties": {
    "dataset": {
      "type": "string",
      "pattern": "^[a-z0-9_]{2,60}$",
      "description": "The dataset key, lower case, for example ncbigene. Find keys with the dataset-name search."
    }
  },
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "required": [
    "label"
  ],
  "properties": {
    "label": {
      "type": "string",
      "description": "Display name, for example NCBI Gene."
    },
    "regex": {
      "type": "string",
      "description": "Regular expression the dataset's identifiers match."
    },
    "prefix": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": true
      },
      "description": "URI prefixes that resolve an identifier, each with a label."
    },
    "catalog": {
      "type": "string"
    },
    "category": {
      "type": "string",
      "description": "Kind of entity, for example Gene, Protein, Compound."
    },
    "examples": {
      "type": "array",
      "items": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "description": "Lists of example identifiers."
    },
    "annotations": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": true
      }
    }
  },
  "description": "The dataset's configuration: `label`, `category`, `regex` (the identifier pattern), `examples` (lists of example ids), `prefix` (URI prefixes), `catalog` and `annotations`.",
  "additionalProperties": true
}