CREW / CrewPay

Launch Pump coin via CrewPay (MAINNET)

crew_launch

Destructive

The launching agent earns 15% of creator fees onchain. Creator fees follow trading volume and can be zero. MAINNET custodial launch: Prefer explicit crew[] (from crew_list_kols). Autohire is a fallback convenience. Creates a Pump.fun coin and locks fee-shares at launch (60/15/25 default; 60/15/5/20 with referral) via Jito [create,lock] then v0+ALT. Prefer non-custodial crew_build_unsigned (mintPubkey required) + signAllTransactions + crew_submit_signed. Approval optional; requires CREW_AGENT_API_KEY + CREW_LAUNCHER_KEY. crew_wire_fees is repair-only.

Input Schema

Name	Required	Description
`crew`	No	Explicit crew (shares must total 100%) overrides Autohire when provided
`mode`	No
`name`	Yes
`seats`	No	Autohire seats when crew omitted
`ticker`	Yes
`twitter`	No	X / Twitter handle or URL
`website`	No
`dryRunId`	No	Optional unless the API key has requireApproval=true
`imageUrl`	No	Public image URL (or use imageBase64)
`agentName`	No
`holderKol`	No	Open Holder-KOL (fees unlocked until crew_lock_holder_kol)
`secretKey`	No	FORBIDDEN — rejected if set.
`agentModel`	No	e.g. claude, gpt, gemini, grok
`privateKey`	No	FORBIDDEN — rejected if set.
`description`	No	≤204 chars; attribution appended to reach ≤240 final
`imageBase64`	No
`launcherKey`	No	FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
`initialBuySol`	No	Dev buy 0–10 SOL (site+API aligned)
`agentObjective`	No
`idempotencyKey`	No	Retry-safe key; replays cached launch for 15m

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 18, 2026
- addedInput schema / properties / crew / items / properties / evmWallet / description
```
Added value: +"Optional 0x… Base address (42 chars) for Zora/Clanker payouts."
```
- addedInput schema / properties / crew / items / properties / handle / description
```
Added value: +"X / Pump handle without @. Example: \"crewpayhq\". Required."
```
- addedInput schema / properties / crew / items / properties / hireRole / description
```
Added value: +"Optional hire role label. One of caller | chart | raid | kol | dev."
```
- addedInput schema / properties / crew / items / properties / share / description
```
Added value: +"Integer percent of the crew slice (1–100). Crew shares must total 100."
```
- addedInput schema / properties / crew / items / properties / wallet / description
```
Added value: +"Solana payout wallet (base58). Required. Example: a KOL wallet from crew_list_kols."
```
Changed2 schema fields changedOct 12, 2026
- addedInput schema / properties / crew / items / properties / evmWallet
```
Added value: +{
+  "maxLength": 42,
+  "minLength": 42,
+  "type": "string"
+}
```
- changedInput schema / properties / crew / items / properties / wallet / minLength
```
Previous value: -32New value: +20
```
Changed2 schema fields changedOct 11, 2026
- changedInput schema / properties / crew / maxItems
```
Previous value: -10New value: +8
```
- changedInput schema / properties / seats / maximum
```
Previous value: -10New value: +8
```

Changed2 schema fields changedOct 11, 2026

changedInput schema / properties / dryRunId / description

Previous value: -"From crew_launch_dry_run after human approval on approvalUrl"New value: +"Optional unless the API key has requireApproval=true"

changedInput schema / required

Previous value: -[
-  "dryRunId",
-  "name",
-  "ticker"
-]New value: +[
+  "name",
+  "ticker"
+]

Changed2 schema fields changedOct 10, 2026

addedInput schema / properties / dryRunId

Added value: +{
+  "description": "From crew_launch_dry_run after human approval on approvalUrl",
+  "maxLength": 64,
+  "minLength": 16,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "name",
-  "ticker"
-]New value: +[
+  "dryRunId",
+  "name",
+  "ticker"
+]

First observedOct 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructive/openWorld/non-idempotent, and the description adds real context on top: 15% agent fee, creator fees can be zero, default fee splits (60/15/25, or 60/15/5/20 with referral), Jito [create,lock] then v0+ALT construction, and required CREW_AGENT_API_KEY + CREW_LAUNCHER_KEY. The Jito/v0+ALT phrasing is terse jargon, keeping it just short of a 5.

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

Conciseness3/5

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

The content is dense and largely earns its place, but it reads as a stream of telegraphic fragments rather than a front-loaded summary, opening on the 15% fee rather than the core action. Structure could be tighter.

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?

For a 20-parameter MAINNET launch with no output schema, the description covers fees, auth keys, approval/optional dry-run, and non-custodial alternatives fairly completely. Minor gaps remain around the repair path and dry-run flow, but nothing an agent needs to invoke it is missing.

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 coverage is 65%, so most parameters are self-documented in the schema. The description only touches crew[] vs Autohire and mintPubkey at a high level, adding little syntax or constraint detail beyond what the schema already provides; a baseline 3 is appropriate.

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?

States a specific verb+resource ("Creates a Pump.fun coin and locks fee-shares at launch") and explicitly separates itself from siblings: crew_build_unsigned is non-custodial, crew_wire_fees is repair-only. An agent can distinguish this custodial MAINNET launch from the unsigned alternatives without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit routing: prefer explicit crew[] sourced from crew_list_kols, Autohire is a fallback, and prefer non-custodial crew_build_unsigned + signAllTransactions + crew_submit_signed. It also flags crew_wire_fees as repair-only, covering when-not-to-use.

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

All CREW / CrewPay tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Launch Pump coin via CrewPay (MAINNET)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources