Skip to main content
Glama
OpenZeppelin

OpenZeppelin Contracts MCP Server

Official
by OpenZeppelin

solidity-stablecoin

Generate ERC-20 stablecoin smart contract source code with configurable features like minting, pausing, voting, and cross-chain bridging for blockchain development.

Instructions

Make a stablecoin token that uses the ERC-20 standard. Experimental, some features are not audited and are subject to change.

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
symbolYesThe short symbol for the token
burnableNoWhether token holders will be able to destroy their tokens
pausableNoWhether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
premintNoThe number of tokens to premint for the deployer.
premintChainIdNoThe chain ID of the network on which to premint tokens.
mintableNoWhether privileged accounts will be able to create more supply or emit more tokens
callbackNoWhether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.
permitNoWhether without paying gas, token holders will be able to allow third parties to transfer from their account.
votesNoWhether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.
flashmintNoWhether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.
crossChainBridgingNoWhether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, or the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. The SuperchainERC20 feature is only available on chains in the Superchain, and requires deploying your contract to the same address on every chain in the Superchain.
namespacePrefixNoThe prefix for ERC-7201 namespace identifiers. It should be derived from the project name or a unique naming convention specific to the project. Used only if the contract includes storage variables and upgradeability is enabled. Default is "myProject".
accessNoThe type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. Managed enables a central contract to define a policy that allows certain callers to access certain functions.
infoNoMetadata about the contract and author
restrictionsNoWhether to restrict certain users from transferring tokens, either via allowing or blocking them. This feature is experimental, not audited and is subject to change.
freezableNoWhether authorized accounts can freeze and unfreeze accounts for regulatory or security purposes. This feature is experimental, not audited and is subject to change.

Implementation Reference

  • The handler function that destructures input parameters into StablecoinOptions and generates the Solidity stablecoin contract code using the OpenZeppelin Wizard's stablecoin.print() method, wrapped in safePrintSolidityCodeBlock.
    async ({
      name,
      symbol,
      burnable,
      pausable,
      premint,
      premintChainId,
      mintable,
      callback,
      permit,
      votes,
      flashmint,
      crossChainBridging,
      access,
      info,
      restrictions,
      freezable,
    }) => {
      const opts: StablecoinOptions = {
        name,
        symbol,
        burnable,
        pausable,
        premint,
        premintChainId,
        mintable,
        callback,
        permit,
        votes,
        flashmint,
        crossChainBridging,
        access,
        info,
        restrictions,
        freezable,
      };
      return {
        content: [
          {
            type: 'text',
            text: safePrintSolidityCodeBlock(() => stablecoin.print(opts)),
          },
        ],
      };
    },
  • Zod schema for the stablecoin tool inputs, extending the ERC20 schema (without upgradeable) with additional restrictions and freezable options.
    export const stablecoinSchema = {
      ...erc20SchemaOmitUpgradeable,
      restrictions: z
        .literal(false)
        .or(z.literal('allowlist'))
        .or(z.literal('blocklist'))
        .optional()
        .describe(solidityStablecoinDescriptions.restrictions),
      freezable: z.boolean().optional().describe(solidityStablecoinDescriptions.freezable),
    } as const satisfies z.ZodRawShape;
  • Registers the 'solidity-stablecoin' MCP tool with the server, specifying the tool name, detailed prompt from Wizard, input schema, and the handler function.
    export function registerSolidityStablecoin(server: McpServer): RegisteredTool {
      return server.tool(
        'solidity-stablecoin',
        makeDetailedPrompt(solidityPrompts.Stablecoin),
        stablecoinSchema,
        async ({
          name,
          symbol,
          burnable,
          pausable,
          premint,
          premintChainId,
          mintable,
          callback,
          permit,
          votes,
          flashmint,
          crossChainBridging,
          access,
          info,
          restrictions,
          freezable,
        }) => {
          const opts: StablecoinOptions = {
            name,
            symbol,
            burnable,
            pausable,
            premint,
            premintChainId,
            mintable,
            callback,
            permit,
            votes,
            flashmint,
            crossChainBridging,
            access,
            info,
            restrictions,
            freezable,
          };
          return {
            content: [
              {
                type: 'text',
                text: safePrintSolidityCodeBlock(() => stablecoin.print(opts)),
              },
            ],
          };
        },
      );
    }
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 behavioral traits: the experimental/unstable nature ('Experimental, some features are not audited and are subject to change'), that it generates source code rather than deploying ('Returns the source code... Does not write to disk'), and the output format ('formatted in a Markdown code block'). This covers important aspects like safety warnings and output behavior.

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 extremely concise and well-structured in just three sentences. The first sentence states the core purpose, the second provides crucial behavioral context (experimental nature), and the third specifies output format and limitation. Every sentence earns its place with no wasted words.

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

Completeness4/5

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

Given the complexity (17 parameters, no output schema, no annotations), the description does a good job covering essential context. It explains what the tool does, its experimental nature, output format, and that it doesn't write to disk. However, for such a complex tool with many parameters and no output schema, it could benefit from more guidance about parameter interactions or typical use cases.

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 17 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

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

Purpose4/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 stablecoin token that uses the ERC-20 standard' and 'Returns the source code of the generated contract'. It specifies the resource (stablecoin token) and action (make/generate), but doesn't explicitly differentiate from sibling tools like 'solidity-erc20' or 'stellar-stablecoin', which would require more specific comparison.

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

Usage Guidelines3/5

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

The description provides some implied usage context by mentioning 'Experimental, some features are not audited and are subject to change', which suggests caution. However, it doesn't explicitly state when to use this tool versus alternatives like 'solidity-erc20' or 'stellar-stablecoin', nor does it provide clear exclusions or prerequisites for usage.

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