Skip to main content
Glama

send-message-to-process

Send a message containing data and optional tags to a specific process on the Flux MCP server for streamlined interaction with the Arweave Operating System.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
processIdYes
tagsNo

Implementation Reference

  • The core handler function for the 'send-message-to-process' tool. It sends a message to the specified AO process using the `message` function from `@permaweb/aoconnect`, waits briefly with `sleep(100)`, retrieves the output using `result`, handles errors, cleans the output with `cleanOutput`, and formats the response as MCP content.
    async ({ processId, data, tags }) => {
      const messageId = await message({
        process: processId,
        signer: this.signer,
        data,
        tags,
      });
      await sleep(100);
      const output = await result({
        message: messageId,
        process: processId,
      });
    
      if (output.Error) {
        return {
          content: [{ type: "text", text: cleanOutput(output.Error) }],
        };
      }
    
      return {
        content: [
          { type: "text", text: cleanOutput(output.Messages[0].Data) },
        ],
      };
    }
  • Zod input schema for the tool: required `processId` (string), `data` (string), optional `tags` (array of objects with `name` and `value` strings). Defines validation for tool parameters.
    {
      processId: z.string(),
      data: z.string(),
      tags: z
        .array(
          z.object({
            name: z.string(),
            value: z.string(),
          })
        )
        .optional(),
    },
  • src/mcp.ts:86-126 (registration)
    Registration of the 'send-message-to-process' tool on the McpServer instance within the FluxServer class's registerTools method. Includes name, description, schema, and inline handler function.
    this.server.tool(
      "send-message-to-process",
      "send a message to an existing AO process",
      {
        processId: z.string(),
        data: z.string(),
        tags: z
          .array(
            z.object({
              name: z.string(),
              value: z.string(),
            })
          )
          .optional(),
      },
      async ({ processId, data, tags }) => {
        const messageId = await message({
          process: processId,
          signer: this.signer,
          data,
          tags,
        });
        await sleep(100);
        const output = await result({
          message: messageId,
          process: processId,
        });
    
        if (output.Error) {
          return {
            content: [{ type: "text", text: cleanOutput(output.Error) }],
          };
        }
    
        return {
          content: [
            { type: "text", text: cleanOutput(output.Messages[0].Data) },
          ],
        };
      }
    );
  • Helper function used by the tool (and others) to clean ANSI escape codes and normalize newlines in JSON-stringified output before returning to the user.
    function cleanOutput(result: any): string {
      if (!result) return "";
    
      return JSON.stringify(result, null, 2)
        .replace(/\\u001b\[\d+m/g, "")
        .replace(/\\n/g, "\n");
    }
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