> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/mcp-and-ai-reference/capabilities-and-version-scope.md).

# Check MCP capabilities and version scope

Use the tools advertised by your authenticated connection to determine what the assistant can attempt. Documentation does not enable an operation on another server, build, tenant or account.

Dublin 6.2.0 includes tools for discovery, authoring, service deployment and execution inspection. The active connection determines which operations are available to your account. Refresh the tool list after an upgrade; a tool count does not identify your installed product version.

## Match the task to a tool family

| Task                            | Advertised operations                                                                            | Required evidence                                                                                            |
| ------------------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| Establish scope                 | `tenants_list`, `tenants_select`                                                                 | Current Hub/tenant/enterprise context; user-selected tenant; permission.                                     |
| Discover native components      | Application, library, action, Work Item and trigger search                                       | Returned IDs, library/version scope and actual inputs/outputs.                                               |
| Build a Hyperflow or Work Item  | `automs_create`, `automs_get_flow`, `automs_set_variables`, `automs_edit_flow`, `automs_release` | Correct Autom kind, draft revision, action references, typed contract and release result.                    |
| Configure native error handling | `automs_edit_flow` with `set_error_handling`, `error_flow` and `error_flow_of`                   | Retry settings, separate handler steps, final Continue or Stop behavior and run logs.                        |
| Configure a native trigger      | `trigger_events_search`, `automs_set_trigger`, trigger condition/status tools                    | Available event, setup schema, registration side effects and verification state.                             |
| Build or revise a Service       | `services_get`, `services_create`, `services_release_version`                                    | Released Work Item versions, valid lanes, Engage contract and phase behavior.                                |
| Prepare a deployment            | Deployment search/read/create/package/update tools                                               | MSP tenant or Enterprise organization scope, version, preserved bindings, connections and environment.       |
| Activate a deployment           | `deployments_go_live`                                                                            | The reviewed package, required permission and confirmation for activation.                                   |
| Run a Hyperflow                 | `automs_run`                                                                                     | Existing API/webhook trigger, declared inputs, idempotency key and execution authorization.                  |
| Run a Service                   | `services_run`                                                                                   | A live deployment with a supported entry in the active scope, its body contract and execution authorization. |
| Inspect outcomes                | Run and Service Case search/read tools                                                           | Execution errors, case result and relevant destination evidence.                                             |
| Handle a checkpoint             | Approval list/get/decide tools                                                                   | Exact pending checkpoint and authorized decision; not a generic case-edit API.                               |
| Extend an application/library   | Application, connection, library/action, Data Manager and trigger-definition tools               | Existing native capability gap, draft/version prerequisites and operation-specific side effects.             |

The [tool index](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools.md) groups operations by task. The active request declaration is authoritative for arguments; examples are not exhaustive response schemas.

## Establish the active context

1. Confirm the intended environment and signed-in account through the supported connection flow.
2. Use `tenants_list` to read the current context. On an MSP Hub connection, Hyperflows, runs, credentials and libraries use tenant context; Work Items, Services and deployments use Hub context according to the reviewed tool description.
3. Use only the tenant selected by the user. An existing choice in the conversation can be retained; do not pick an unrelated tenant because it is the only result.
4. Record the product build when a supported product view provides it. A tool count or documentation date does not identify the build.
5. Read the current tool schema, exact field types, enum values and discovery prerequisites.
6. Refresh context after a scope, account, version or connection change. Tenant selection changes the connection context for later tools; do not interleave Hub and tenant calls as if they were independent.

Enterprise and tenant-bound connections may not permit tenant switching. Respect the `selectable` result.

## Distinguish planning, publication and execution

`automs_create` creates an initial draft for Hyperflows or Work Items. **Applying `services_create` creates a Service blueprint and publishes its initial version.** Do not label Service create apply as draft-only.

A blueprint version, a deployment draft, a live deployment and a completed Service Case are separate states. A successful preview is not a runtime test. A successful publish is not evidence that a target application changed.

Use preview/apply only where the active tool supports it. Honor its confirmation requirements. Preserve an expected revision where the edit schema provides it; do not invent revision arguments for tools that do not expose them.

## Keep contracts separate

| Contract               | Defines                                                                      |
| ---------------------- | ---------------------------------------------------------------------------- |
| MCP request            | Arguments accepted by one tool.                                              |
| Library action         | Action configuration, native inputs and declared outputs.                    |
| Hyperflow input/output | Values accepted and returned by the selected runnable Autom.                 |
| Work Item contract     | Published version, binding inputs, skills and declared response.             |
| Service plan           | Engage and phase composition, pinned Work Items, behavior and outcome.       |
| Deployment             | Bindings, organization or tenant scope, environment, package and activation. |

A required Work Item input can come from verified context, Engage, an earlier output or a permitted lookup. It is not automatically a question for the user. Use [input resolution](https://docs.autommate.com/userguide/mcp-and-ai-reference/deployment-input-resolution.md).

A schema labelled Object is not a complete property schema. An Example Response is not proof that a Stop action returns those fields. A native application record is not proof of an available App Trigger.

## Validate a capability before relying on it

Retain the exact tool names, request declarations, context and versions. Read the resulting objects back after an authorized write. For runtime claims, record a controlled request, the matching run or Service Case, errors and the verified destination outcome.

Use cancellation and approval operations only when they are advertised by your connection, and follow their documented state requirements. Re-running a failed request is not rollback. Use only a matching advertised operation and its actual semantics.

For the implementation sequence, use [structured service authoring](https://docs.autommate.com/userguide/mcp-and-ai-reference/structured-service-authoring.md), [native discovery](https://docs.autommate.com/userguide/mcp-and-ai-reference/native-app-trigger-and-data-discovery.md) and [deployment input resolution](https://docs.autommate.com/userguide/mcp-and-ai-reference/deployment-input-resolution.md).
