CREW / CrewPay

Wire / repair CREW fee-shares

crew_wire_fees

Destructive

Create and permanently lock Pump.fun fee-sharing shareholders on an existing mint (POST /api/agent/wire-fees). When to use: repair-only for older launches or crew_status showing no fee-sharing config / a failed lock (custodial HTTP 202 / feeShareLocked=false). Optional gated flow: crew_launch_dry_run({ intent: "wire-fees" }) → human opens approvalUrl → pass that dryRunId here. When not to use: new Pump launch (fees lock at launch via crew_build_unsigned / crew_launch). Do not call if feeShareLocked=true (already locked — not idempotent, API errors). Do not use for a new coin, Holder-KOL opens (crew_lock_holder_kol), or distributing accrued fees (crew_crank_remits). Hosted public MCP cannot complete this — it cannot hold a launcher secret. Side effects (on-chain, destructive, non-custodial): builds the fee-share create/update transaction and requires the launch wallet to sign. Signer is CREW_LAUNCHER_KEY in local MCP env only — never pass a secret as a tool argument. CrewPay does not custody keys or funds. Writes the Pump.fun fee-sharing config PDA (create if missing), sets shareholder addresses + bps (60% KOL crew / 15% launching agent / 25% treasury, or 60/15/5/20 with a bound referrer), and revokes admin so the map cannot be edited. Also persists feeShareLocked on the CrewPay board. Does not transfer SOL, move LP, or launch a mint. Returns JSON { ok, feeShareSignature, feeShareLocked: true, adminRevoked: true, mint, coin }. Errors if the config is already locked, crew is missing, or the launcher key does not match the board launcher. Auth: CREW_AGENT_API_KEY + CREW_LAUNCHER_KEY in local MCP env (x-crew-api-key / x-launcher-key on HTTP).

Input Schema

Name	Required	Description
`crew`	No	Optional array of 1–8 crew members {handle, wallet, share, hireRole?}. Shares must total 100. Omit to reuse the crew stored on the board from launch.
`mint`	Yes	Required. Solana Pump.fun mint (base58, 32–64 chars, no 0/O/I/l). Example: a mint from crew_list_launches or the crew_launch response.
`mode`	No	Optional desk mode. One of agent \| split \| buyback \| raid. Default agent.
`name`	No	Optional coin name (≤32 chars) if the mint is not already on the board. Example: "Desk Cat".
`ticker`	No	Optional ticker (≤13 chars). Example: "DESK". Omit to reuse the board ticker.
`dryRunId`	No	Optional string (16–64 chars) unless the API key has requireApproval=true. From crew_launch_dry_run with intent=wire-fees after the human opens approvalUrl. Example: a 32-char opaque id.
`secretKey`	No	FORBIDDEN — rejected if set.
`privateKey`	No	FORBIDDEN — rejected if set.
`launcherKey`	No	FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 18, 2026

changedInput schema / properties / crew / description

Previous value: -"Optional — omit to reuse board crew from launch"New value: +"Optional array of 1–8 crew members {handle, wallet, share, hireRole?}. Shares must total 100. Omit to reuse the crew stored on the board from launch."

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

changedInput schema / properties / dryRunId / description

Previous value: -"Optional unless the API key has requireApproval=true"New value: +"Optional string (16–64 chars) unless the API key has requireApproval=true. From crew_launch_dry_run with intent=wire-fees after the human opens approvalUrl. Example: a 32-char opaque id."

addedInput schema / properties / mint / description

Added value: +"Required. Solana Pump.fun mint (base58, 32–64 chars, no 0/O/I/l). Example: a mint from crew_list_launches or the crew_launch response."

addedInput schema / properties / mode / description

Added value: +"Optional desk mode. One of agent | split | buyback | raid. Default agent."

addedInput schema / properties / name / description

Added value: +"Optional coin name (≤32 chars) if the mint is not already on the board. Example: \"Desk Cat\"."

addedInput schema / properties / ticker / description

Added value: +"Optional ticker (≤13 chars). Example: \"DESK\". Omit to reuse the board ticker."

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
```
Changed1 schema field changedOct 11, 2026
- changedInput schema / properties / crew / maxItems
```
Previous value: -10New value: +8
```

Changed2 schema fields changedOct 11, 2026

changedInput schema / properties / dryRunId / description

Previous value: -"From crew_launch_dry_run intent=wire-fees after human wallet approval"New value: +"Optional unless the API key has requireApproval=true"

changedInput schema / required

Previous value: -[
-  "dryRunId",
-  "mint"
-]New value: +[
+  "mint"
+]

Changed2 schema fields changedOct 11, 2026

addedInput schema / properties / dryRunId

Added value: +{
+  "description": "From crew_launch_dry_run intent=wire-fees after human wallet approval",
+  "maxLength": 64,
+  "minLength": 16,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "mint"
-]New value: +[
+  "dryRunId",
+  "mint"
+]

First observedOct 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already flag destructive/non-idempotent/open-world, and the description adds substantial context beyond them: what on-chain state is written (fee-sharing PDA, shareholder addresses + bps split, admin revocation), that it is non-custodial, that the signer must be CREW_LAUNCHER_KEY locally, that secrets must never be passed as arguments, and that it errors if already locked or the key mismatches. This aligns with, rather than contradicts, idempotentHint=false.

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?

Long, but front-loaded with the verb+scope then organized into When-to-use / When-not-to-use / side-effects / returns / auth blocks so an agent can scan it. Dense yet largely every sentence carries a distinct constraint, with only minor redundancy in the secret-handling warnings.

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?

For a destructive, multi-parameter, non-custodial transaction builder with no output schema, the description covers prerequisites, gating flow, side effects, return shape, and error conditions. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value: it explains that the crew array may be omitted to reuse the board crew, that shares follow fixed splits (60/15/25 or 60/15/5/20), and that dryRunId comes from crew_launch_dry_run after the human opens approvalUrl. It does not restate mint/ticker/name semantics beyond the schema.

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 ('Create and permanently lock Pump.fun fee-sharing shareholders on an existing mint') and immediately delimits scope ('on an existing mint'), which separates it from crew_launch/crew_build_unsigned that create new launches.

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?

Explicit 'When to use' (repair-only for older launches or crew_status showing no fee-sharing config), explicit 'When not to use' (new launch, Holder-KOL opens, fee distribution), and names the alternatives (crew_lock_holder_kol, crew_crank_remits, crew_launch_dry_run). It even flags the hosted-MCP limitation that makes the tool unusable there.

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.

Wire / repair CREW fee-shares

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources