Skip to main content
Glama
OpenZeppelin

OpenZeppelin Contracts MCP Server

Official
by OpenZeppelin

cairo-multisig

Generate multi-signature smart contracts requiring quorum approval for transaction execution. Create secure Cairo contracts with configurable signers and upgrade options.

Instructions

Make a multi-signature smart contract, requiring a quorum of registered signers to approve and collectively execute transactions.

Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the contract
quorumYesThe minimal number of confirmations required by the Multisig to approve a transaction.
upgradeableNoWhether the smart contract is upgradeable.
infoNoMetadata about the contract and author

Implementation Reference

  • The handler function that executes the cairo-multisig tool. It takes input parameters, constructs MultisigOptions, generates Cairo code using the external multisig.print function from @openzeppelin/wizard-cairo, and returns it as text content.
    async ({ name, quorum, upgradeable, info }) => {
      const opts: MultisigOptions = {
        name,
        quorum,
        upgradeable,
        info,
      };
      return {
        content: [
          {
            type: 'text',
            text: safePrintCairoCodeBlock(() => multisig.print(opts)),
          },
        ],
      };
    },
  • Zod schema defining the input parameters for the cairo-multisig tool: name, quorum, upgradeable, and info.
    export const multisigSchema = {
      name: z.string().describe(commonDescriptions.name),
      quorum: z.string().describe(cairoMultisigDescriptions.quorum),
      upgradeable: commonSchema.upgradeable,
      info: commonSchema.info,
    } as const satisfies z.ZodRawShape;
  • Direct registration of the 'cairo-multisig' tool on the MCP server, including the tool name, prompt, schema, and handler.
    return server.tool(
      'cairo-multisig',
      makeDetailedPrompt(cairoPrompts.Multisig),
      multisigSchema,
      async ({ name, quorum, upgradeable, info }) => {
        const opts: MultisigOptions = {
          name,
          quorum,
          upgradeable,
          info,
        };
        return {
          content: [
            {
              type: 'text',
              text: safePrintCairoCodeBlock(() => multisig.print(opts)),
            },
          ],
        };
      },
    );
  • Top-level call to register all Cairo tools, including cairo-multisig, on the main MCP server.
    registerCairoTools(server);
  • Registration entry for Multisig tool in the Cairo tools registry, which calls the specific registerCairoMultisig function.
    Multisig: () => registerCairoMultisig(server),
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behaviors: the tool generates contract source code (not writes to disk), returns it in Markdown format, and requires a quorum for transaction approval. However, it lacks details on permissions, rate limits, or error handling, which would be helpful for a mutation tool.

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

Conciseness5/5

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

The description is front-loaded with the core purpose in the first sentence, followed by output format and disk behavior. Both sentences earn their place with essential information, and there's no wasted text.

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

Completeness3/5

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

Given no annotations and no output schema, the description covers the core functionality and output format adequately. However, for a tool that creates smart contracts (a complex mutation), it lacks details on security implications, error cases, or what 'registered signers' entails, leaving some gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters (name, quorum, upgradeable, info). The description adds no parameter-specific information beyond what's in the schema, meeting the baseline for high coverage.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Make a multi-signature smart contract, requiring a quorum of registered signers to approve and collectively execute transactions.' It specifies the verb ('Make'), resource ('multi-signature smart contract'), and distinguishes from siblings by focusing on multisig functionality rather than other contract types like ERC20 or account.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., cairo-account, cairo-erc20, solidity-multisig), it doesn't specify scenarios where multisig is preferred over other contract types or language choices (Cairo vs. Solidity).

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

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/OpenZeppelin/contracts-wizard'

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