Skip to main content
Glama
OpenZeppelin

OpenZeppelin Contracts MCP Server

Official
by OpenZeppelin

stellar-non-fungible

Generate SEP-50 compliant non-fungible token contracts with customizable features like burnable, enumerable, pausable, and upgradeable options. Returns contract source code in Markdown format without writing to disk.

Instructions

Make a non-fungible token per the Non-Fungible Token Standard, compatible with SEP-50, similar to ERC-721.

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
tokenUriNoThe metadata URI returned by the token contract for every NFT.
burnableNoWhether token holders will be able to destroy their tokens
enumerableNoWhether the NFTs are enumerable (can be iterated over).
consecutiveNoTo batch mint NFTs instead of minting them individually (sequential minting is mandatory).
pausableNoWhether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
mintableNoWhether privileged accounts will be able to create more supply or emit more tokens
sequentialNoWhether the IDs of the minted NFTs will be sequential.
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

Implementation Reference

  • Async handler function that constructs NonFungibleOptions from input parameters and generates Rust code using nonFungible.print(opts), wrapped in safePrintRustCodeBlock.
    async ({
      name,
      symbol,
      tokenUri,
      burnable,
      enumerable,
      consecutive,
      pausable,
      mintable,
      sequential,
      upgradeable,
      info,
    }) => {
      const opts: NonFungibleOptions = {
        name,
        symbol,
        tokenUri,
        burnable,
        enumerable,
        consecutive,
        pausable,
        mintable,
        sequential,
        upgradeable,
        info,
      };
      return {
        content: [
          {
            type: 'text',
            text: safePrintRustCodeBlock(() => nonFungible.print(opts)),
          },
        ],
      };
    },
  • Zod schema defining the input parameters for the stellar-non-fungible tool, including name, symbol, various optional flags, and common schema.
    export const nonFungibleSchema = {
      name: z.string().describe(commonDescriptions.name),
      symbol: z.string().describe(commonDescriptions.symbol),
      tokenUri: z.string().optional().describe(stellarNonFungibleDescriptions.tokenUri),
      burnable: z.boolean().optional().describe(commonDescriptions.burnable),
      enumerable: z.boolean().optional().describe(stellarNonFungibleDescriptions.enumerable),
      consecutive: z.boolean().optional().describe(stellarNonFungibleDescriptions.consecutive),
      pausable: z.boolean().optional().describe(commonDescriptions.pausable),
      mintable: z.boolean().optional().describe(commonDescriptions.mintable),
      sequential: z.boolean().optional().describe(stellarNonFungibleDescriptions.sequential),
      ...commonSchema,
    } as const satisfies z.ZodRawShape;
  • Registration function that registers the 'stellar-non-fungible' tool on the MCP server with its prompt, schema, and handler.
    export function registerStellarNonFungible(server: McpServer): RegisteredTool {
      return server.tool(
        'stellar-non-fungible',
        makeDetailedPrompt(stellarPrompts.NonFungible),
        nonFungibleSchema,
        async ({
          name,
          symbol,
          tokenUri,
          burnable,
          enumerable,
          consecutive,
          pausable,
          mintable,
          sequential,
          upgradeable,
          info,
        }) => {
          const opts: NonFungibleOptions = {
            name,
            symbol,
            tokenUri,
            burnable,
            enumerable,
            consecutive,
            pausable,
            mintable,
            sequential,
            upgradeable,
            info,
          };
          return {
            content: [
              {
                type: 'text',
                text: safePrintRustCodeBlock(() => nonFungible.print(opts)),
              },
            ],
          };
        },
      );
    }
Behavior3/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 usefully states that the tool 'Returns the source code of the generated contract, formatted in a Markdown code block' and 'Does not write to disk', which clarifies output format and side effects. However, it doesn't mention authentication requirements, rate limits, error conditions, or other behavioral traits.

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 with just two sentences that efficiently convey the tool's purpose, output format, and key behavioral constraint. Every word earns its place with 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?

For a complex tool with 12 parameters, no annotations, and no output schema, the description is minimal but covers the essential purpose and output format. It adequately explains what the tool does at a high level but lacks details about when to use it, behavioral constraints beyond disk writing, or how the output should be interpreted.

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?

The schema description coverage is 100%, so the schema already documents all 12 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, which meets the baseline expectation when schema coverage is high.

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 'Make[s] a non-fungible token' and specifies it's 'compatible with SEP-50, similar to ERC-721', which provides a specific verb+resource. However, it doesn't explicitly differentiate from sibling tools like 'stellar-fungible' or 'cairo-erc721', which would be needed for a score of 5.

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 like 'stellar-fungible' or other NFT-related tools in the sibling list. It mentions compatibility with SEP-50 but doesn't explain when this specific implementation is preferred over other options.

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