Skip to main content
Glama

run-lua-in-process

Execute Lua code within a specified process on the Flux MCP server, enabling dynamic script execution and interaction with AO systems without manual coding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
processIdYes
tagsNo

Implementation Reference

  • Core handler logic for executing Lua code in an AO process by sending an 'Eval' message and retrieving the output.
    export async function runLuaCode(
      code: string,
      processId: string,
      signer: any,
      tags?: { name: string; value: string }[]
    ) {
      const messageId = await message({
        process: processId,
        signer,
        data: code,
        tags: [{ name: "Action", value: "Eval" }, ...(tags || [])],
      });
    
      await sleep(100);
    
      const outputResult = await result({
        message: messageId,
        process: processId,
      });
    
      if (outputResult.Error) {
        return JSON.stringify(outputResult.Error);
      }
    
      return JSON.stringify(outputResult.Output.data);
    }
  • src/mcp.ts:169-190 (registration)
    Registers the 'run-lua-in-process' tool on the MCP server, including input schema and thin wrapper handler.
    this.server.tool(
      "run-lua-in-process",
      "run a lua script in an existing AO process",
      {
        code: z.string(),
        processId: z.string(),
        tags: z
          .array(
            z.object({
              name: z.string(),
              value: z.string(),
            })
          )
          .optional(),
      },
      async ({ code, processId, tags }) => {
        const result = await runLuaCode(code, processId, this.signer, tags);
        return {
          content: [{ type: "text", text: cleanOutput(result) }],
        };
      }
    );
  • Zod input schema for the tool parameters: code, processId, and optional tags.
    {
      code: z.string(),
      processId: z.string(),
      tags: z
        .array(
          z.object({
            name: z.string(),
            value: z.string(),
          })
        )
        .optional(),
    },
  • Alternative registration of the 'run-lua-in-process' tool in the local server script.
    server.tool(
      "run-lua-in-process",
      {
        code: z.string(),
        processId: z.string(),
        tags: z
          .array(
            z.object({
              name: z.string(),
              value: z.string(),
            })
          )
          .optional(),
      },
      async ({ code, processId, tags }) => {
        const result2 = await runLuaCode(code, processId, tags);
        return {
          content: [
            {
              type: "text",
              text: cleanOutput(result2),
            },
          ],
        };
      }
    );
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