<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Guides on AgentOps</title><link>https://samyn92.github.io/agentops/docs/guides/</link><description>Recent content in Guides on AgentOps</description><generator>Hugo</generator><language>en</language><atom:link href="https://samyn92.github.io/agentops/docs/guides/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Custom MCP Tools</title><link>https://samyn92.github.io/agentops/docs/guides/building-tools/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://samyn92.github.io/agentops/docs/guides/building-tools/</guid><description>&lt;p&gt;This guide walks through creating a custom MCP tool server from scratch using the &lt;code&gt;mcputil&lt;/code&gt; SDK, packaging it, and deploying it into an AgentOps-managed agent.&lt;/p&gt;
&lt;h2 id="prerequisites"&gt;Prerequisites&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Go 1.25+&lt;/li&gt;
&lt;li&gt;&lt;code&gt;agent-tools&lt;/code&gt; CLI installed (or use &lt;code&gt;make push-server&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Access to an OCI registry (e.g. &lt;code&gt;ghcr.io&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;A running AgentOps cluster with the operator installed&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="1-create-a-go-module"&gt;1. Create a Go Module&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;mkdir servers/my-tool &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd&lt;/span&gt; servers/my-tool
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;go mod init github.com/myorg/agent-tools/servers/my-tool
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;go get github.com/modelcontextprotocol/go-sdk@v0.8.0
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Add the shared &lt;code&gt;mcputil&lt;/code&gt; SDK as a local dependency:&lt;/p&gt;</description></item><item><title>Multi-Agent Orchestration</title><link>https://samyn92.github.io/agentops/docs/guides/multi-agent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://samyn92.github.io/agentops/docs/guides/multi-agent/</guid><description>&lt;p&gt;AgentOps supports multi-agent orchestration natively. An orchestrator agent discovers and delegates to task agents using built-in runtime tools — no custom wiring required.&lt;/p&gt;
&lt;p&gt;This guide walks through setting up an orchestrator + task agent pattern.&lt;/p&gt;
&lt;h2 id="how-delegation-works"&gt;How Delegation Works&lt;/h2&gt;
&lt;p&gt;The delegation flow is:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The orchestrator agent calls &lt;code&gt;list_task_agents&lt;/code&gt; (built-in) to discover available task agents in its namespace.&lt;/li&gt;
&lt;li&gt;It decides which agents to delegate to based on their descriptions and tags.&lt;/li&gt;
&lt;li&gt;It calls &lt;code&gt;run_agents&lt;/code&gt; (built-in) with target agent names and input.&lt;/li&gt;
&lt;li&gt;The runtime creates &lt;code&gt;AgentRun&lt;/code&gt; CRs for each delegated task.&lt;/li&gt;
&lt;li&gt;The &lt;code&gt;DelegationWatcher&lt;/code&gt; tracks progress via Kubernetes Watch on those AgentRun resources.&lt;/li&gt;
&lt;li&gt;Results are collected and returned to the orchestrator when all delegated runs complete.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The orchestrator does not need any &lt;code&gt;toolRefs&lt;/code&gt; for delegation — &lt;code&gt;list_task_agents&lt;/code&gt; and &lt;code&gt;run_agents&lt;/code&gt; are built into the Fantasy runtime. However, the orchestrator can also have its own tools for direct work.&lt;/p&gt;</description></item></channel></rss>