OpenZeppelin Solidity Contracts

Solidity ERC20

solidity-erc20

Make a fungible token per the ERC-20 standard.

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

Input Schema

Name	Required	Description
`info`	No	Metadata about the contract and author
`name`	Yes	The name of the contract
`votes`	No	Whether to keep track of historical balances for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps.
`access`	No	The 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.
`permit`	No	Whether without paying gas, token holders will be able to allow third parties to transfer from their account.
`symbol`	Yes	The short symbol for the token
`premint`	No	The number of tokens to premint for the deployer.
`burnable`	No	Whether token holders will be able to destroy their tokens
`callback`	No	Whether to include support for code execution after transfers and approvals on recipient contracts in a single transaction.
`decimals`	No	The number of decimals used to represent token amounts. Defaults to 18.
`mintable`	No	Whether privileged accounts will be able to create more supply or emit more tokens
`pausable`	No	Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
`flashmint`	No	Whether to include built-in flash loans to allow lending tokens without requiring collateral as long as they're returned in the same transaction.
`upgradeable`	No	Whether the smart contract is upgradeable. Transparent uses more complex proxy with higher overhead, requires less changes in your contract. Can also be used with beacons. UUPS uses simpler proxy with less overhead, requires including extra code in your contract. Allows flexibility for authorizing upgrades.
`chainlinkAce`	No	Chainlink ACE (Automated Compliance Engine) adds token policy enforcement through a separately deployed and configured policy engine (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ace). Defaults to false (disabled). Requires ownable or roles access; combining ACE with CCIP requires roles. This integration does not support ACE together with managed access, Callback (ERC-1363), Flash Minting, a nonzero premint, or bridge modes other than CCIP. Configure policies and register the token with the engine before use; this does not establish legal compliance. Enabling ACE makes the generated contract use BUSL-1.1, overriding info.license. Review the ACE license (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/LICENSE) and additional use grants (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/chainlink-ace-License-grants) before production use.
`premintChainId`	No	The chain ID of the network on which to premint tokens.
`namespacePrefix`	No	The 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".
`crossChainBridging`	No	Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are custom bridges on any chain, Chainlink CCIP with a separately configured BurnMintTokenPool (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ccip), to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. CCIP requires role-based access control, granting the configured pool MINTER_ROLE on each supported chain, and BURNER_ROLE when Burnable is disabled. With Burnable enabled, any holder can burn their own tokens, including the pool, and burnFrom requires an allowance. 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.
`crossChainLinkAllowOverride`	No	Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to "erc7786native".

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / chainlinkAce

Added value: +{
+  "description": "Chainlink ACE (Automated Compliance Engine) adds token policy enforcement through a separately deployed and configured policy engine (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ace). Defaults to false (disabled). Requires ownable or roles access; combining ACE with CCIP requires roles. This integration does not support ACE together with managed access, Callback (ERC-1363), Flash Minting, a nonzero premint, or bridge modes other than CCIP. Configure policies and register the token with the engine before use; this does not establish legal compliance. Enabling ACE makes the generated contract use BUSL-1.1, overriding info.license. Review the ACE license (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/LICENSE) and additional use grants (https://github.com/smartcontractkit/chainlink-ace/blob/v1.2.0/chainlink-ace-License-grants) before production use.",
+  "type": "boolean"
+}

changedInput schema / properties / crossChainBridging / anyOf

Previous value: -[
-  {
-    "anyOf": [
-      {
-        "const": "custom",
-        "type": "string"
-      },
-      {
-        "const": "erc7786native",
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "const": "superchain",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "anyOf": [
+          {
+            "const": "custom",
+            "type": "string"
+          },
+          {
+            "const": "chainlink-ccip",
+            "type": "string"
+          }
+        ]
+      },
+      {
+        "const": "erc7786native",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "const": "superchain",
+    "type": "string"
+  }
+]

changedInput schema / properties / crossChainBridging / description

Previous value: -"Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use 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."New value: +"Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are custom bridges on any chain, Chainlink CCIP with a separately configured BurnMintTokenPool (integration guide: https://docs.openzeppelin.com/chainlink-ccip-ace; Chainlink docs: https://docs.chain.link/ccip), to embed an ERC-7786 based bridge directly in the token contract, or to use the SuperchainERC20 standard with the predeployed SuperchainTokenBridge. CCIP requires role-based access control, granting the configured pool MINTER_ROLE on each supported chain, and BURNER_ROLE when Burnable is disabled. With Burnable enabled, any holder can burn their own tokens, including the pool, and burnFrom requires an allowance. 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."

changedInput schema / properties / info / properties / license / description

Previous value: -"The license used by the contract, default is \"MIT\""New value: +"The license used by the contract, default is \"MIT\". Ignored when chainlinkAce is enabled: contracts generated with ACE always use BUSL-1.1."

Changed1 schema field changedAug 10, 2026

changedInput schema / properties / crossChainBridging / description

Previous value: -"Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use 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."New value: +"Whether to allow authorized bridge contracts to mint and burn tokens for crosschain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use 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."

Changed1 schema field changedJun 30, 2026

addedInput schema / properties / decimals

Added value: +{
+  "description": "The number of decimals used to represent token amounts. Defaults to 18.",
+  "type": "string"
+}

Changed3 schema fields changedFeb 26, 2026

changedInput schema / properties / crossChainBridging / anyOf

Previous value: -[
-  {
-    "const": "custom",
-    "type": "string"
-  },
-  {
-    "const": "superchain",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "anyOf": [
+      {
+        "const": "custom",
+        "type": "string"
+      },
+      {
+        "const": "erc7786native",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "const": "superchain",
+    "type": "string"
+  }
+]

changedInput schema / properties / crossChainBridging / description

Previous value: -"Whether 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."New value: +"Whether to allow authorized bridge contracts to mint and burn tokens for cross-chain transfers. Options are to use custom bridges on any chain, to embed an ERC-7786 based bridge directly in the token contract, or to use 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."

addedInput schema / properties / crossChainLinkAllowOverride

Added value: +{
+  "description": "Whether to allow replacing a crosschain link that has already been registered. Only used if crossChainBridging is set to \"erc7786native\".",
+  "type": "boolean"
+}

First observedJan 31, 2026

TDQS

A3.6/5.0

Behavior4/5

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

No annotations are supplied, so the description carries full behavioral burden, and it does disclose the two most important traits: the tool returns source code (not a deployed artifact) formatted as a Markdown code block, and it does not write to disk. These side-effect and output statements are non-obvious and genuinely useful. It is silent on param interdependencies, though the schema itself covers those.

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?

Two short sentences with zero filler, front-loading purpose before the output and side-effect disclosures. Every sentence earns its place.

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?

For a 19-parameter code generator with no output schema, the description usefully explains the return value (Markdown code block of source) and confirms no disk write, which is what an agent most needs. The remaining gap is the absence of any routing guidance among the many sibling generators.

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 baseline is 3. The description adds no parameter-level meaning beyond what the schema already documents in detail (including the chainlinkAce and crossChainBridging caveats), so it neither helps nor hurts.

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?

States a specific verb and resource ('Make a fungible token per the ERC-20 standard') that an agent can sharply distinguish from erc721/erc1155 siblings. It does not differentiate itself from near-neighbors like solidity-stablecoin or stylus-erc20, but the ERC-20 reference is specific enough to anchor selection.

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?

There is no when-to-use or when-not-to-use guidance. With siblings like solidity-stablecoin, solidity-rwa, cairo-erc20, and stylus-erc20, the agent is left to infer which generator applies; the description never names an alternative or a selecting condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OpenZeppelin Solidity Contracts tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?