Skip to main content
Glama
OpenZeppelin

OpenZeppelin Contracts MCP Server

Official
by OpenZeppelin

stellar-stablecoin

Generate a Stellar-compatible stablecoin smart contract using OpenZeppelin's Fungible Token Standard. Configure token properties like minting, pausing, and access controls to create a customized stablecoin implementation.

Instructions

Make a stablecoin that uses Fungible Token Standard, compatible with SEP-41.

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.
mintableNoWhether privileged accounts will be able to create more supply or emit more tokens
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.
upgradeableNoWhether the contract can be upgraded.
infoNoMetadata about the contract and author
limitationsNoWhether to restrict certain users from transferring tokens, either via allowing or blocking them.

Implementation Reference

  • The handler function for the 'stellar-stablecoin' tool. It takes input parameters, constructs StablecoinOptions, calls stablecoin.print(opts) from '@openzeppelin/wizard-stellar' to generate Rust code, and formats it safely for output.
    async ({ name, symbol, burnable, pausable, premint, mintable, upgradeable, access, limitations, info }) => {
      const opts: StablecoinOptions = {
        name,
        symbol,
        burnable,
        pausable,
        premint,
        mintable,
        upgradeable,
        access,
        limitations,
        info,
      };
      return {
        content: [
          {
            type: 'text',
            text: safePrintRustCodeBlock(() => stablecoin.print(opts)),
          },
        ],
      };
    },
  • Zod schema for validating inputs to the 'stellar-stablecoin' tool, extending fungibleSchema with 'limitations' option specific to stablecoins.
    export const stablecoinSchema = {
      ...fungibleSchema,
      limitations: z
        .literal(false)
        .or(z.literal('allowlist'))
        .or(z.literal('blocklist'))
        .optional()
        .describe(stellarStablecoinDescriptions.limitations),
    } as const satisfies z.ZodRawShape;
  • Registers the 'stellar-stablecoin' tool on the MCP server, providing the tool name, prompt, schema, and handler function.
    export function registerStellarStablecoin(server: McpServer): RegisteredTool {
      return server.tool(
        'stellar-stablecoin',
        makeDetailedPrompt(stellarPrompts.Stablecoin),
        stablecoinSchema,
        async ({ name, symbol, burnable, pausable, premint, mintable, upgradeable, access, limitations, info }) => {
          const opts: StablecoinOptions = {
            name,
            symbol,
            burnable,
            pausable,
            premint,
            mintable,
            upgradeable,
            access,
            limitations,
            info,
          };
          return {
            content: [
              {
                type: 'text',
                text: safePrintRustCodeBlock(() => stablecoin.print(opts)),
              },
            ],
          };
        },
      );
    }
  • Top-level registration function for all Stellar tools, including 'stellar-stablecoin' via registerStellarStablecoin.
    export function registerStellarTools(server: McpServer) {
      Object.values(getRegisterFunctions(server)).forEach(registerTool => {
        registerTool(server);
      });
    }
  • Calls registerStellarTools during MCP server initialization, thereby registering the 'stellar-stablecoin' tool.
    registerStellarTools(server);
    registerStylusTools(server);
    registerUniswapHooksTools(server);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'Returns the source code... Does not write to disk,' which clarifies output format and non-destructive behavior, but fails to address critical aspects like error handling, performance, or security implications for a code-generation tool with 10 parameters.

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 highly concise and front-loaded, with two sentences that efficiently convey the tool's purpose and output behavior without redundancy. Every sentence adds value, making it easy to parse quickly.

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 the complexity (10 parameters, no output schema, no annotations), the description is minimally adequate. It covers the core purpose and output format but lacks details on error cases, dependencies, or integration context, which are important for a code-generation tool in a blockchain ecosystem with many sibling alternatives.

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 fully documents all 10 parameters. The description adds no parameter-specific information beyond what the schema provides, such as explaining how parameters interact or default behaviors. Baseline 3 is appropriate as the schema handles parameter documentation.

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 specific action ('Make a stablecoin') and resource ('that uses Fungible Token Standard, compatible with SEP-41'), distinguishing it from sibling tools like 'stellar-fungible' or 'solidity-stablecoin' by specifying the Stellar blockchain context and SEP-41 compatibility.

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?

No explicit guidance on when to use this tool versus alternatives like 'stellar-fungible' or 'solidity-stablecoin' is provided. The description implies usage for generating SEP-41-compatible stablecoin contracts but lacks context on prerequisites, limitations, or comparisons to siblings.

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