Skip to content
decodecodeveloper docs
Studio → MCP Apps and extensions → Configure agents

Creating Agents

Configure a focused role, instructions, and selected connection tools in Studio

An agent combines a role, instructions, and a selected set of connection tools. Start with the outcome it should own, then give it only the context and capabilities needed for that work.

Creating Agents with Deco Chat

You can configure an agent from the + / Browse agents entry and its Settings panel. Set the instructions, attach connections, and choose the individual tools it can use. See Quickstart.

When the assistant has agent-management tools, you can also ask it to create the configuration:

Create a support-triage agent for our team. It should read tickets from the
connected help desk, summarize the issue, preserve the original ticket link,
and suggest the next action. It should not edit customer records.

The current management flow inspects connections with COLLECTION_CONNECTIONS_LIST / GET, creates the agent with COLLECTION_VIRTUAL_MCP_CREATE, and verifies the saved configuration with COLLECTION_VIRTUAL_MCP_GET. Creation uses a focused title, description, selected connectionIds, instructions, and conversation starters. These operations require the corresponding organization permissions.

What Goes on Under the Hood?

Instructions

Write the role, desired outcome, allowed capabilities, and constraints. A concrete workflow is more useful than a broad instruction to be helpful:

Role: Support triage for our internal support team.
 
Workflow:
1. Read the ticket and relevant account context using connected tools.
2. Summarize the problem and preserve links to the original records.
3. Suggest the next action and identify missing information.
 
Constraints:
- Do not edit support or customer records.
- Do not invent a tool result when a connection is unavailable.

Connections and tools

Connections live under Settings → Connections at the organization level. In the agent's Settings, attach the relevant connections and select their tools. Match the selection to the instructions: if an agent is meant to summarize tickets, it needs the tools that read them. See Connections.

Files and context

Attach the files or connected data sources needed for the role. A connection's existence does not guarantee that every document has been indexed or that the agent can access every record. See Context and tasks.

Conversation starters

Provide a few prompts that show the agent's intended work, such as “Summarize ticket 123” or “Review today's urgent requests.” The management tool accepts these through its prompts field.

Test and refine

Start a conversation with a representative request. Check which tools the agent used, whether the answer follows the instructions, and whether it preserves the source evidence. Update the instructions or tool selection, then repeat with a different case.

For an existing configuration, inspect it with COLLECTION_VIRTUAL_MCP_GET, apply the focused change with COLLECTION_VIRTUAL_MCP_UPDATE, and verify the saved result.

Next steps

Implementation reference: agent guide. Reviewed 2026-10-05.