Well-curated set of 8 focused tools for Solidity contract generation. Tools follow consistent naming patterns (solidity-<type>) and have clear, descriptive names. Descriptions explain purpose, expected output format, and notable constraints. Input schemas use typed parameters with meaningful descriptions rather than generic request bodies. All tools document optional boolean/enum features with context about trade-offs (e.g., 'Increases gas cost of transfers'). Minor issues: schema definitions are truncated in provided data, making full schema validation impossible; some parameter descriptions are incomplete in the submission. The domain focus (smart contract generation) is narrow and well-defined, suggesting intentional curation rather than auto-generation.
Make an account contract that follows the ERC-4337 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Make a custom smart contract. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Make a non-fungible token per the ERC-1155 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
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.
Make a non-fungible token per the ERC-721 standard. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Make a contract to implement governance, such as for a DAO. Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Schema definitions truncated in submission data - cannot fully validate parameter completeness, required vs optional status, or enum constraints
Parameter descriptions incomplete in provided data (e.g., 'premint' cut off mid-description in tools 1, 4, 5; 'uriStorage' cut off in tool 2; 'pausable' cut off in tool 3)
Experimental/unaudited features (stablecoin, rwa) lack detail about which specific features are experimental or what changes may occur
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-03-24 | C | 68 | 2025-11-25 | v1 |
Make a real-world asset 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.
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.