Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Start an agent session

create_agent_session

Start an agent session and queue a first prompt, receiving replies asynchronously through session history. Target either your own session or an incident's shared session.

Instructions

Start a session with an agent and send it a first prompt. The agent replies asynchronously: this returns once the prompt is queued, and the reply is read from GET /sessions/{session_id}/history/messages. incidentId names the incident the session is about. With sessionMode USER, the default, the session is the caller's own, so it needs an OAuth token or a user API key, and a workspace API key gets 400. With INCIDENT it is the incident's, visible across the workspace, and an incident's open session takes the prompt instead of a new one starting. With hidden true the prompt still runs the turn, but its prompt.accepted history event is marked hidden so a client can leave it out of the conversation. Needs a grant to run the agent, and to view the incident when incidentId is set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>",
      "prompt": "<prompt>"
    },
    "name": "create_agent_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
effortNo
hiddenNo
promptYes
agentIdYes
modelIdNo
incidentIdNo
sessionModeNoUSER
pipelineEditorContextNo
X-Orchestra-Account-IdNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.11.13-0
    • addedInput schema / properties / hidden
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv2026.10.29-0
    • addedInput schema / properties / sessionMode
      Added value: +{
      +  "default": "USER",
      +  "enum": [
      +    "USER",
      +    "INCIDENT"
      +  ],
      +  "type": "string"
      +}
  3. Addedv2026.10.12-0

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds async semantics, history read path, 400 failure mode, session sharing, and hidden-event behavior far beyond the readOnly/destructive annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and dense; each sentence states a distinct operational fact with no restatement of title or schema types.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers auth, ownership, incident scoping and async reply path; optional tuning parameters remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Explains incidentId, sessionMode and hidden deeply, but leaves effort, modelId, pipelineEditorContext and agentId undocumented at 11% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource plus the composite action of sending a first prompt, which separates it from send_agent_session_message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains USER vs INCIDENT selection, open-session reuse, credential and grant requirements; only an explicit named follow-up alternative is absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools