Skip to main content
Glama
OpenZeppelin

OpenZeppelin Contracts MCP Server

Official
by OpenZeppelin

stellar-governor

Create a governor smart contract for token-based on-chain governance. Customizable voting parameters, timelock, and access control.

Instructions

Make a governor contract for on-chain governance using token-based voting.

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
versionNoThe semantic version label returned by the governor contract.
votingDelayNoNumber of ledgers between proposal creation and voting start (17,000 ledgers are approx. 1 day).
votingPeriodNoNumber of ledgers during which voting remains open (120,000 ledgers are approx. 1 week).
proposalThresholdNoMinimum voting power required for creating a proposal, default is 100.
quorumNoMinimum number of votes required for a proposal to pass, default is 500.
timelockNoWhether to add a timelock mechanism that enforces a delay between proposal queuing and execution.
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.
explicitImplementationsNoWhether the contract should use explicit trait implementations instead of using the default ones provided by the library.
upgradeableNoWhether the contract can be upgraded.
infoNoMetadata about the contract and author
Behavior3/5

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

With no annotations, the description partially compensates by stating it returns source code in a Markdown code block and does not write to disk. However, it omits other behavioral details such as whether it interacts with any external systems, requires network access, or has any side effects beyond code generation.

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 sentences, front-loaded with the core purpose, and no extraneous information. Every sentence adds value.

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 11 parameters, a nested object, no output schema, and no annotations, the description is moderately complete. It conveys the main function and a key behavioral trait (no disk write), but lacks deeper context about governance setup, default values, or relationship to sibling tools.

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 baseline is 3. The description adds no parameter-specific details beyond what the schema already provides, but the schema itself has thorough descriptions for each parameter.

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 it creates a governor contract for on-chain governance using token-based voting, which is a specific verb+resource. It also mentions the output format. However, among sibling governor tools (cairo-governor, solidity-governor), the description does not explicitly differentiate that this is for Stellar, but the tool name itself provides that context.

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 offers no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what it does without contextual usage advice.

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