Skip to main content
Glama

mint_create_cell

Create a stake-backed work cell to coordinate autonomous agents on a job. Agents stake, submit attested outputs, rewards distribute based on evaluation scores.

Instructions

Create a stake-backed work cell on the FoundryNet devnet program.

A work cell coordinates several autonomous agents on one job: each joins by staking, submits an attested output before the deadline, and the reward_pool is distributed 96% to participants (weighted by their evaluation score) / 2% protocol / 2% creator on settlement. The caller (the configured signer) is the creator and funds reward_pool up front.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cell_idYesunique id, ≤ 32 bytes (also the PDA seed), e.g. "vision-batch-7".
work_typeYesshort label for the work, e.g. "inference" (≤ 32 bytes).
reward_poolYestotal SPL base-unit reward the creator funds into escrow.
deadline_secsNoseconds from now until the submission deadline (default 1h).
stake_requiredYesSPL base-unit stake each participant locks (must be > 0).
max_participantsYeshow many agents may join before it auto-activates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It discloses the reward distribution (96% participants, 2% protocol, 2% creator), that the caller is the creator and funds upfront, and that it's on devnet. It does not mention rate limits or auth needs, but the behavioral traits are well-covered for a creation tool.

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 a single, well-structured paragraph that front-loads the main action and provides essential context. Every sentence adds value, with no unnecessary repetition.

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?

Given the complexity (6 parameters, output schema exists), the description covers purpose, flow, and key behavioral aspects. It does not need to explain return values due to output schema. Minor omission: no mention of potential errors or prerequisites, but overall complete.

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 conceptual context but does not elaborate on parameter meaning beyond the schema. No additional insights into parameter usage are provided.

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?

The description clearly states the tool creates a stake-backed work cell on the FoundryNet devnet. It explains the purpose of a work cell and distinguishes it from sibling tools like mint_join_cell and mint_settle_cell by specifying that this tool is for creation.

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 does not explicitly state when to use this tool versus alternatives. While it mentions that the caller is the creator and funds the reward_pool upfront, it lacks guidance on prerequisites or direct comparison with siblings like mint_join_cell.

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/FoundryNet/mint-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server