Skip to main content
Adam exposes focused tools for projects, tasks, conversations, and files. Your client only sees tools allowed by the permissions granted during authentication.

Context and models

Billing and integrations

Automations

Projects

Tasks and conversations

The model object contains the model slug, the fast option, and an optional effort of low, medium, high, or xhigh. Call adam_list_models instead of guessing a model slug.

Files

Use adam_upload_attachment, then pass the returned upload ID in the attachments array of adam_create_task or adam_send_message. Upload IDs expire after 24 hours. For durable shared inputs, use adam_upload_project_file instead. Use adam_delete_project_file only after the user confirms which shared project file to remove.

Run a task reliably

1

Inspect the connection

Use adam_get_context when the client needs to confirm the connected user, workspace, or permissions.
2

Resolve IDs instead of guessing

Use the list tools to find project IDs and model slugs. Adam validates project and task IDs as UUIDs.
3

Create the task once

Pass a new UUID as idempotencyKey to adam_create_task. Reuse that key only when retrying the exact same operation.
4

Poll at a sensible interval

Call adam_get_task until the status is completed, failed, cancelled, or awaiting_input. Do not start a duplicate task while the first one runs.
5

Handle input or collect files

Answer a pending interaction with adam_answer_interaction. After completion, use adam_list_files to find the resulting files and adam_get_file to retrieve a resource link.

Example requests

Continue a task that needs input

Review completed project work

Update and continue existing work

Last modified on August 26, 2026