Export ontology release

When to use

Use extension__ontology__get_export to export a published ontology release for another tool or standards-based consumer. The response includes the exact release ID, source manifest digest, exported document, media type, document digest, adapter version, and a loss report. Inspect that report before giving the document to a consumer: RDF and OWL are supported interchange subsets, not the Registry’s native storage model. Use the stable ontology_... artifact ID with an exact Atlan rel_... release ID. Specify adapter_version when reproducibility matters. For rdf, owl, and skos, profile and base_iri are required even though the tool schema marks them optional. base_iri sets the identifiers: it must be an absolute HTTP or HTTPS IRI that ends in / or #, with no spaces and at most 2,048 characters. Export never changes the release.

Inputs

In search mode, the default, run this tool through mcp__call_read_tool, the runner its run_with names: send the inputs below as its arguments, and put session_id and rationale beside them, not inside. In full mode, open a session with mcp__initialise first and pass its session_id. The authenticated mcp__describe_tools result in search mode, or tools/list response in full mode, is the final check for the tool name and schema available to your account.

Input	Type	Required	Meaning
`ontology_id`	string	Yes	Ontology artifact handle owning the release line.
`release_id`	string	Yes	Exact `rel_…` release ID.
`format`	string	Yes	Values: `native_json`, `rdf`, `owl`, `skos`.
`serialization`	string	Yes	Values: `json`, `turtle`, `json_ld`.
`adapter_version`	string	No	Pin the versioned adapter for reproducible output.
`profile`	string	No	Required for RDF, OWL, and SKOS. See Interchange formats.
`base_iri`	string	No	Required for RDF, OWL, and SKOS: an absolute HTTP(S) IRI ending in `/` or `#`.
`rationale`	string	Yes	Why this call advances the user’s task. In search mode, send it beside `arguments` instead.
`session_id`	string	Yes	The session ID returned by `mcp__initialise`. Replace the example value with your own. In search mode, send the `session_id` from `mcp__search_tools` beside `arguments` instead.

Example

The example shows the tool’s arguments in full mode. In search mode, send them, without session_id and rationale, as arguments to mcp__call_tool, with session_id and rationale beside them. Replace the object, release, and session IDs with values you can access.

{
  "ontology_id": "ontology_01example",
  "release_id": "rel_01example",
  "format": "native_json",
  "serialization": "json",
  "adapter_version": "native-json/1",
  "session_id": "mcp_session_<your-session-id>",
  "rationale": "I need this released context to answer the user’s question accurately."
}

Permissions and result

This tool is read-only and uses your authenticated identity and workspace permissions. Check the returned release and digest where present, and inspect truncated on bounded retrieval results before relying on completeness. See Use Ontology with agents for the full workflow and MCP Gateway errors for connection and permission failures.

Get started

Tool references

When to use

Inputs

Example

Permissions and result