Skip to main content
Glama

run-handler-using-handler-name

Execute specific handlers on Flux MCP server by providing process ID, handler name, and data, enabling automated code and handler management within the Arweave Operating System.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
handlerNameYes
processIdYes

Implementation Reference

  • src/mcp.ts:257-279 (registration)
    Registers the MCP tool 'run-handler-using-handler-name' with input schema, description, and a thin async handler that delegates to the runHandler helper function from helpers/handlers.ts.
    this.server.tool(
      "run-handler-using-handler-name",
      "run a handler using its name in an existing AO process",
      { processId: z.string(), handlerName: z.string(), data: z.string() },
      async ({ processId, handlerName, data }) => {
        const result = await runHandler(
          processId,
          handlerName,
          data,
          this.signer
        );
        if (result.Error) {
          return {
            content: [{ type: "text", text: cleanOutput(result.Error) }],
          };
        }
        return {
          content: [
            { type: "text", text: cleanOutput(result.Messages[0].Data) },
          ],
        };
      }
    );
  • Zod schema defining the input parameters for the tool: processId, handlerName, and data.
    { processId: z.string(), handlerName: z.string(), data: z.string() },
  • Core helper function that implements the logic to run a named handler in an AO process by sending a message with 'Action' tag set to handlerName and the provided data, then retrieving the result using aoconnect APIs.
    export async function runHandler(
      processId: string,
      handlerName: string,
      data: string,
      signer: any
    ) {
      const messageId = await message({
        process: processId,
        signer,
        data,
        tags: [{ name: "Action", value: handlerName }],
      });
    
      await sleep(100);
    
      const outputResult = await result({
        message: messageId,
        process: processId,
      });
    
      return outputResult;
    }
  • Alternative registration of the same tool in the local development server (src/local/index.js), using an inline runHandler implementation.
    server.tool(
      "run-handler-using-handler-name",
      { processId: z.string(), handlerName: z.string(), data: z.string() },
      async ({ processId, handlerName, data }) => {
        const result2 = await runHandler(processId, handlerName, data);
        if (result2.Error) {
          return {
            content: [{ type: "text", text: cleanOutput(result2.Error) }],
          };
        }
        return {
          content: [{ type: "text", text: cleanOutput(result2.Messages[0].Data) }],
        };
      }
    );
  • Inline helper function runHandler in local/index.js, identical logic to the exported one in helpers/handlers.ts.
    async function runHandler(processId, handlerName, data) {
      const messageId = await message({
        process: processId,
        signer,
        data,
        tags: [{ name: "Action", value: handlerName }],
      });
      await sleep(100);
      const outputResult = await result({
        message: messageId,
        process: processId,
      });
      return outputResult;
    }
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