Skip to main content
Glama

load-blueprint

Load and process blueprints from a specified URL and process ID using Flux, an AI-powered MCP server, to automate workflows with Arweave Operating System.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processIdYes
urlYes

Implementation Reference

  • src/mcp.ts:192-202 (registration)
    Registers the 'load-blueprint' MCP tool, defining its input schema ({url, processId}) and handler logic that fetches the blueprint code from the URL and executes it in the target process using runLuaCode.
    this.server.tool(
      "load-blueprint",
      "load a blueprint in an existing AO process",
      { url: z.string(), processId: z.string() },
      async ({ url, processId }) => {
        const code = await fetchBlueprintCode(url);
        const result = await runLuaCode(code, processId, this.signer);
        return {
          content: [{ type: "text", text: cleanOutput(result) }],
        };
      }
  • Helper function fetchBlueprintCode used by the load-blueprint handler to retrieve the Lua blueprint code from the specified URL.
    export async function fetchBlueprintCode(url: string) {
      const response = await fetch(url);
      const code = await response.text();
      return code;
  • Alternative registration of the 'load-blueprint' tool in the local JS version, with identical schema and handler logic.
    "load-blueprint",
    { url: z.string(), processId: z.string() },
    async ({ url, processId }) => {
      const code = await fetchBlueprintCode(url);
      const result2 = await runLuaCode(code, processId);
      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