CREW / CrewPay

Dry-run a CREW launch (no chain tx)

crew_launch_dry_run

Read-onlyIdempotent

The launching agent earns 15% of creator fees onchain. Creator fees follow trading volume and can be zero. Dry-run a launch (default) or wire-fees (intent=wire-fees). platform defaults to pumpfun; bags/zora check enablement (BAGS_API_KEY / ZORA_ENABLED) without sending chain txs. Prefer explicit crew[] from crew_list_kols; Autohire is a fallback. Returns dryRunId + approvalUrl. Requires CREW_AGENT_API_KEY.

Input Schema

Name	Required	Description
`crew`	No
`mint`	No	Required when intent=wire-fees
`mode`	No
`name`	No
`seats`	No
`intent`	No	launch (default) or wire-fees
`ticker`	No
`twitter`	No
`website`	No
`imageUrl`	No	Public image URL (or use imageBase64)
`platform`	No
`agentName`	No
`holderKol`	No
`secretKey`	No	FORBIDDEN — rejected if set.
`agentModel`	No
`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
`agentObjective`	No
`launcherPubkey`	No	Optional public launcher address for balance check (never a secret)

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."
```

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "pumpfun",
-  "bags",
-  "zora",
-  "clanker",
-  "vibevibe"
-]New value: +[
+  "pumpfun",
+  "bags",
+  "zora",
+  "clanker",
+  "vibevibe",
+  "sui"
+]

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "pumpfun",
-  "bags",
-  "zora",
-  "clanker"
-]New value: +[
+  "pumpfun",
+  "bags",
+  "zora",
+  "clanker",
+  "vibevibe"
+]

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "pumpfun",
-  "bags",
-  "zora"
-]New value: +[
+  "pumpfun",
+  "bags",
+  "zora",
+  "clanker"
+]

Changed5 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
```
- changedInput schema / properties / crew / maxItems
```
Previous value: -8New value: +100
```
- changedInput schema / properties / launcherPubkey / minLength
```
Previous value: -32New value: +20
```
- addedInput schema / properties / platform
```
Added value: +{
+  "enum": [
+    "pumpfun",
+    "bags",
+    "zora"
+  ],
+  "type": "string"
+}
```
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
```

Changed3 schema fields changedOct 11, 2026

addedInput schema / properties / intent

Added value: +{
+  "description": "launch (default) or wire-fees",
+  "enum": [
+    "launch",
+    "wire-fees"
+  ],
+  "type": "string"
+}

addedInput schema / properties / mint

Added value: +{
+  "description": "Required when intent=wire-fees",
+  "maxLength": 64,
+  "minLength": 32,
+  "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,64}$",
+  "type": "string"
+}

removedInput schema / required

Removed value: -[
-  "name",
-  "ticker"
-]

First observedOct 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value beyond them: the required credential (CREW_AGENT_API_KEY), the return payload (dryRunId + approvalUrl), the enablement preconditions (BAGS_API_KEY / ZORA_ENABLED), and the caveat that creator fees can be zero. It does not describe what the dry run validates or the approval flow's next step, so not 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 is not front-loaded: the opening sentence is an economics aside ('launching agent earns 15% of creator fees... can be zero') while the actual purpose ('Dry-run a launch') appears only in the third sentence. An agent scanning the first line does not learn what the tool does.

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?

There is no output schema, and the description does cover the return identifiers and the auth requirement, which is good. But for a 22-parameter tool with 36% schema coverage and no required fields, large parts of the input surface remain unexplained, so the definition is adequate rather than 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 coverage is only 36% across 22 parameters, so the description must carry weight, and it does explain the highest-value ones (intent semantics, platform default and enablement, crew[] sourcing). However, most parameters (mode, seats, name, ticker, initialBuySol, the forbidden secret fields, etc.) receive no description-level explanation, leaving the coverage gap only partially closed.

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 names a specific action and scope: 'Dry-run a launch (default) or wire-fees (intent=wire-fees)' and clarifies it works 'without sending chain txs.' This distinguishes it from the actual-mutation siblings crew_launch and crew_wire_fees, though it never names those siblings explicitly, so the differentiation is implied rather than stated.

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?

It gives concrete routing guidance: 'Prefer explicit crew[] from crew_list_kols; Autohire is a fallback,' and states platform defaults and intent defaults. What is missing is any explicit when-to-use-this-vs-crew_launch framing (e.g., 'call this first to preview before the real launch'), so it stops short of full alternative routing.

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.

Dry-run a CREW launch (no chain tx)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources