Skip to main content
Glama

spawn

Automate code and handler creation, testing, and execution within the Arweave Operating System using natural language, eliminating the need for manual coding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needsSqliteNo
tagsYes

Implementation Reference

  • src/mcp.ts:59-84 (registration)
    Full registration of the 'spawn' MCP tool, including inline Zod schema for parameters and the async handler function that spawns an AO process using the imported 'spawn' from @permaweb/aoconnect, selecting module based on 'needsSqlite' flag.
    this.server.tool(
      "spawn",
      "spawn a new AO process",
      {
        tags: z.array(
          z.object({
            name: z.string(),
            value: z.string(),
          })
        ),
        needsSqlite: z.boolean().optional(),
      },
      async ({ tags, needsSqlite }) => {
        const processId = await spawn({
          module: needsSqlite
            ? "33d-3X8mpv6xYBlVB-eXMrPfH5Kzf6Hiwhcv0UA10sw"
            : "JArYBF-D8q2OmZ4Mok00sD2Y_6SYEQ7Hjx-6VZ_jl3g",
          signer: this.signer,
          scheduler: "_GQ33BkPtZrqxA84vM8Zk-N2aO0toNNu_C-l-rawrBA",
          tags,
        });
        return {
          content: [{ type: "text", text: processId }],
        };
      }
    );
  • The core handler logic for the 'spawn' tool: calls the external 'spawn' function with process module (SQLite or standard), signer, scheduler, and tags; returns the processId as text content.
      const processId = await spawn({
        module: needsSqlite
          ? "33d-3X8mpv6xYBlVB-eXMrPfH5Kzf6Hiwhcv0UA10sw"
          : "JArYBF-D8q2OmZ4Mok00sD2Y_6SYEQ7Hjx-6VZ_jl3g",
        signer: this.signer,
        scheduler: "_GQ33BkPtZrqxA84vM8Zk-N2aO0toNNu_C-l-rawrBA",
        tags,
      });
      return {
        content: [{ type: "text", text: processId }],
      };
    }
  • Zod schema for 'spawn' tool inputs: array of name-value tags and optional boolean for SQLite needs.
    {
      tags: z.array(
        z.object({
          name: z.string(),
          value: z.string(),
        })
      ),
      needsSqlite: z.boolean().optional(),
    },
  • Duplicate registration of the 'spawn' tool in the local standalone script, identical implementation to the main server.
    server.tool(
      "spawn",
      {
        tags: z.array(
          z.object({
            name: z.string(),
            value: z.string(),
          })
        ),
        needsSqlite: z.boolean().optional(),
      },
      async ({ tags, needsSqlite }) => {
        const processId = await spawn({
          module: needsSqlite
            ? "33d-3X8mpv6xYBlVB-eXMrPfH5Kzf6Hiwhcv0UA10sw"
            : "JArYBF-D8q2OmZ4Mok00sD2Y_6SYEQ7Hjx-6VZ_jl3g",
          signer,
          scheduler: "_GQ33BkPtZrqxA84vM8Zk-N2aO0toNNu_C-l-rawrBA",
          tags,
        });
        return {
          content: [{ type: "text", text: processId }],
        };
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asrvd/flux'

If you have feedback or need assistance with the MCP directory API, please join our Discord server