> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Recipes

> Small, reviewable MCP request patterns for orienting, inspecting, and resolving OrgX work.

These are request patterns, not recorded workspace results. IDs, records, and
response fields vary by workspace and client. Use the [MCP Tools
Reference](/docs/api/mcp-tools) as the source of truth for the current schema.

## Recipe 1: Establish context and search

Use a bootstrap call when the client needs a session context, then search the
active workspace without changing business records.

```json theme={"dark"}
{
  "tool": "orgx_bootstrap",
  "args": {
    "client_name": "<client_name>",
    "timezone": "<IANA_timezone>"
  }
}
```

```json theme={"dark"}
{
  "tool": "orgx_search",
  "args": {
    "type": "initiative",
    "status": "active",
    "limit": 10,
    "session_id": "<session_id>"
  }
}
```

Review the returned records before selecting one for deeper inspection. A
search result is not evidence that work is complete or shipped.

## Recipe 2: Inspect a decision with context

Use `orgx_inspect` when you have a specific decision ID and need its available
context before making a judgment.

```json theme={"dark"}
{
  "tool": "orgx_inspect",
  "args": {
    "type": "decision",
    "id": "<decision_id>",
    "hydrate_context": true,
    "session_id": "<session_id>"
  }
}
```

Review the decision's observable rationale, evidence, artifact references,
scope, and current status.

## Recipe 3: Resolve an approved decision

Only approve after the decision and its evidence have been shown to the human
reviewer. Use an idempotency key for the write.

```json theme={"dark"}
{
  "tool": "orgx_decide",
  "args": {
    "action": "approve",
    "decision_id": "<decision_id>",
    "note": "Approved after reviewing the artifact and evidence",
    "idempotency_key": "<unique_key>",
    "session_id": "<session_id>"
  }
}
```

Approval records the human decision. Any follow-on work remains subject to the
connected tool's authorization, OrgX policy, and the actual execution receipt.
Approval is not proof that an external system accepted, merged, deployed, or
published the work.

## Choosing the next action

Use `orgx_recommend` when the user asks what to do next or wants a brief. Treat
the result as a recommendation, not an instruction; ask for explicit
confirmation before a separate write action.

```json theme={"dark"}
{
  "tool": "orgx_recommend",
  "args": {
    "mode": "next_action",
    "workspace_id": "<workspace_id>",
    "limit": 5,
    "session_id": "<session_id>"
  }
}
```

## Related references

* [Agent Quickstart](/docs/agent-ops/agent-quickstart)
* [MCP Protocol](/docs/api/mcp-protocol)
* [MCP Tools Reference](/docs/api/mcp-tools)
* [Decisions](/docs/platform/decisions)