Skip to main content
Glama
OpenZeppelin

OpenZeppelin Contracts MCP Server

Official
by OpenZeppelin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Stellar Vault

stellar-vault

Make a tokenized vault that issues Fungible Token shares for an underlying asset, similar to ERC-4626.

Instructions

Make a tokenized vault that issues Fungible Token shares for an underlying asset, similar to ERC-4626.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoNoMetadata about the contract and author
nameYesThe name of the contract
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.
symbolYesThe short symbol for the token
pausableNoWhether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response.
upgradeableNoWhether the contract can be upgraded.
decimalsOffsetNoVirtual decimals offset added to the underlying asset decimals to derive the vault share decimals, used to mitigate inflation (donation) attacks via virtual shares. With the default of 0, diluting a single deposit is never profitable, but an attacker holding most of the shares can profit once enough deposits land at an inflated price. Higher values make attacks orders of magnitude more costly, at the cost of virtual shares absorbing a tiny portion of the value accrued to the vault. Must be between 0 and 10.
explicitImplementationsNoWhether the contract should use explicit trait implementations instead of using the default ones provided by the library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.11
    • changedInput schema / properties / decimalsOffset / description
      Previous value: -"Virtual decimals offset added to the underlying asset decimals to derive the vault share decimals, used to mitigate inflation (donation) attacks via virtual shares. The default of 0 is already safe: it makes such attacks non-profitable. Higher values make attacks orders of magnitude more costly, at the cost of virtual shares absorbing a tiny portion of the value accrued to the vault. Must be between 0 and 10."New value: +"Virtual decimals offset added to the underlying asset decimals to derive the vault share decimals, used to mitigate inflation (donation) attacks via virtual shares. With the default of 0, diluting a single deposit is never profitable, but an attacker holding most of the shares can profit once enough deposits land at an inflated price. Higher values make attacks orders of magnitude more costly, at the cost of virtual shares absorbing a tiny portion of the value accrued to the vault. Must be between 0 and 10."
  2. Addedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose two important traits: the output is Markdown-wrapped source code and nothing is written to disk (a non-destructive generation tool). It stops short of saying whether the code is compiled, tested, or which framework/library it targets, which would be valuable for a generator.

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 purpose and followed by the return contract. No filler, no restatement of the title.

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?

Eight parameters with a nested info object and no output schema make this a complex generator, and the description covers the return shape but not the generated artifact's scope — e.g. whether the chosen options (access, pausable, upgradeable) materially change the emitted code, or where the code can be used. Adequate but with clear gaps for a config-heavy tool.

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%, including a detailed explanation of decimalsOffset and the access enum, so the schema already does the semantic heavy lifting. The description adds only that shares are issued against an underlying asset, implying the name/symbol/decimals context but nothing parameter-specific beyond the schema. Baseline 3 applies.

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?

Specific verb ('Make') plus a precise resource: a tokenized vault issuing Fungible Token shares for an underlying asset. The 'similar to ERC-4626' analogy immediately separates it from siblings like stellar-fungible, stellar-stablecoin, and stellar-non-fungible without the agent needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly defines the use case (you want a vault, not a plain token), but never states when to choose this over stellar-fungible or stellar-stablecoin, nor any prerequisites. Usage must be inferred from the resource description rather than being stated as guidance.

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

Deploy Server

Other Tools