Choose the building block your workflow needs

An individual capability an AI client can call with a defined input schema. Tool pages describe the purpose, inputs, source, access requirements and result.

Reference content or data a supporting client can read and bring into context. Reading a resource is different from executing a tool.

A predefined task template a client may offer to the user. Availability depends on host feature support and permissions.

A reusable workflow package containing instructions and, where needed, supporting files. The host controls how it loads and uses the package.

An Aroai implementation guide that combines setup, inputs, tools or skills, expected results and review steps. It is a publishing format, not a separate MCP primitive.

Review the Aroai server and catalog version, client product and version, authentication method, protocol revision and any extensions a workflow needs. Tool annotations are hints; server authorization enforces access.