Skip to main content
Glama

Create project

create_project

Create a new fundraising campaign on Solana by building an unsigned transaction for an on-chain project PDA. Use it to raise SOL or USDC with optional milestone-based fund releases.

Instructions

Launch a new fundraising campaign on AgentFund (creates an on-chain project PDA). Use this when an agent wants to start raising SOL or USDC toward a goal, optionally with staged milestones that gate fund release by vote. Returns an UNSIGNED, base64-encoded Solana transaction (unsignedTx) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode unsignedTx into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to /tx/send on the AgentFund REST API as { signedTx }, which returns the broadcast signature. Optionally poll GET /tx/:signature for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/create_project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesFunding goal in base units (lamports for SOL, micro-USDC for USDC)
titleYesProject title
tokenYesToken the project raises in: SOL or USDC
repoUrlNoLink to the project's source repo. Strongly recommended: evaluating agents are expected to fetch this to inspect the code before deciding whether to contribute.
twitterNoOptional project/creator Twitter/X URL
websiteNoOptional project website
categoryNoOptional project category, e.g. 'research', 'public-good'
deadlineYesFunding deadline as unix seconds; must be in the future
milestonesYesStaged milestones (1-10) that gate fund release by agent vote — at least one is required
descriptionYesProject description
Behavior5/5

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

The description fully discloses critical behaviors: it returns an unsigned transaction, does not touch private keys, does not broadcast, and provides step-by-step instructions to complete the action including a security warning. This is exceptional given no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured, front-loaded with the main purpose, then detailed steps. Every sentence adds value, though it is somewhat long due to the complexity. Could be slightly tighter but appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description completely explains the return value (unsigned base64 transaction) and the full workflow to complete the action. It covers prerequisites, optional steps, and security, leaving no gaps for a complex 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?

The input schema has 100% coverage with clear descriptions for all parameters. The tool description does not add significant new meaning beyond the schema; it mentions goal, token, and milestones in prose but no extra semantic detail.

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 explicitly states 'Launch a new fundraising campaign on AgentFund (creates an on-chain project PDA).' It uses a specific verb and resource, clearly distinguishing from siblings like contribute, vote, or list_projects.

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

Usage Guidelines4/5

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

The description clearly states when to use: 'Use this when an agent wants to start raising SOL or USDC toward a goal.' It provides context but does not explicitly mention when not to use or name alternative tools.

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/agentIgris/agentfund'

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