`get_term`

Pack: ebi-ols · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

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

Term details. Pass either iri, short_form, or obo_id (the latter two require ontology).

Parameters

Name	Type	Required	Description
`ontology`	string	yes
`iri`	string	no	Full term IRI (preferred).
`short_form`	string	no
`obo_id`	string	no	OBO id, e.g. “EFO:0000408”

Example call

Arguments

{
  "ontology": "efo",
  "obo_id": "EFO:0000408"
}

curl

curl -X POST https://gateway.pipeworx.io/ebi-ols/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_term","arguments":{"ontology":"efo","obo_id":"EFO:0000408"}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('get_term', {
  "ontology": "efo",
  "obo_id": "EFO:0000408"
});

More examples

{
  "ontology": "mondo",
  "short_form": "MONDO:0005148"
}

Response shape

Full JSON Schema

{
  "type": "object",
  "description": "Detailed term information including definition, relationships, and annotations"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

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

Connect to just the ebi-ols pack

{
  "mcpServers": {
    "ebi-ols": {
      "url": "https://gateway.pipeworx.io/ebi-ols/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

get_term