Get bounded ontology context

When to use

Use extension__ontology__get_context to give an agent the smallest relevant part of a published ontology without mixing draft or latest versions. include accepts object_types, interface_types, link_types, shared_property_types, action_types, concept_schemes, and concepts. The response identifies the exact release and manifest digest, explains why each resource was selected, and reports its traversal depth and estimated token cost. Use the stable ontology_... artifact ID with an exact Atlan rel_... release ID. The tool does not accept the retired ontology_release artifact kind. Check truncated before relying on the result. When it is true, follow the returned refinement hints or request different bounds. The service searches only resources visible to the caller, filters them to the selected release, and expands typed dependencies within the requested limits.

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.
`query`	string	Yes	Business task or search terms.
`include`	array	No
`max_resources`	integer	No	Range: 1–50.
`max_depth`	integer	No	Range: 0–4.
`max_tokens`	integer	No	Range: 1–32,000.
`diagnostics`	boolean	No	Include retrieval diagnostics.
`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",
  "query": "customers and orders",
  "max_resources": 15,
  "max_depth": 2,
  "max_tokens": 12000,
  "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

Get bounded ontology context

When to use

Inputs

Example

Permissions and result