Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Record completed work

ship_move
Destructive

Record completion only after the founder explicitly confirms it. Use prepared_result after reviewing the current prepared attempt, or independent_work when the founder completed it separately. Site changes need a live published_url to ship; with planned_url they stay prepared. This records an attestation; it never publishes anything. Free; requires the 'act' scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "move_id": "<move_id>",
      "completion_kind": "<completion_kind>",
      "job_id": "<job_id>",
      "attempt_id": "<attempt_id>",
      "founder_confirmed": "<founder_confirmed>"
    },
    "name": "ship_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
job_idYesship_move_args.job_id.
move_idYesMove id (uuid), from list_feed.
attempt_idYesship_move_args.attempt_id.
final_textNoOptional. Only the words the founder actually posted, exactly as they went out; never your rewrite or the draft. Used only to learn how they write, for a post or reply they published; it marks nothing published. Omit it if unknown.
planned_urlNoA merged own-site change's page: we check it and ship it when the text is live, or after two days.
published_urlNoThe actual public URL, when the completed task has one. This is distinct from a prepared asset.
completion_kindYesindependent_work: your user did it themselves; prepared_result: they confirmed the prepared result.
founder_confirmedYes
expected_move_stateNoship_move_args.expected_move_state; required for independent_work.
expected_legacy_stateNoship_move_args.expected_legacy_state.
expected_move_updated_atNoship_move_args.expected_move_updated_at; required for independent_work.
expected_legacy_updated_atNoship_move_args.expected_legacy_updated_at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / attempt_id / description
      Added value: +"ship_move_args.attempt_id."
    • addedInput schema / properties / completion_kind / description
      Added value: +"independent_work: your user did it themselves; prepared_result: they confirmed the prepared result."
    • changedInput schema / properties / expected_legacy_state / description
      Previous value: -"get_move: prepared_result.legacy_state ?? state."New value: +"ship_move_args.expected_legacy_state."
    • addedInput schema / properties / expected_legacy_updated_at / description
      Added value: +"ship_move_args.expected_legacy_updated_at."
    • changedInput schema / properties / expected_move_state / description
      Previous value: -"Required with expected_move_updated_at for independent_work."New value: +"ship_move_args.expected_move_state; required for independent_work."
    • changedInput schema / properties / expected_move_updated_at / description
      Previous value: -"Required with expected_move_state for independent_work."New value: +"ship_move_args.expected_move_updated_at; required for independent_work."
    • addedInput schema / properties / job_id / description
      Added value: +"ship_move_args.job_id."
  2. Changed1 schema field changed
    • changedInput schema / properties / planned_url / description
      Previous value: -"Future address of a prepared page on the founder's own site."New value: +"A merged own-site change's page: we check it and ship it when the text is live, or after two days."
  3. Changed1 schema field changed
    • addedInput schema / properties / final_text
      Added value: +{
+  "description": "Optional. Only the words the founder actually posted, exactly as they went out; never your rewrite or the draft. Used only to learn how they write, for a post or reply they published; it marks nothing published. Omit it if unknown.",
+  "maxLength": 20000,
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / planned_url
      Added value: +{
+  "description": "Future address of a prepared page on the founder's own site.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / expected_legacy_state / description
      Added value: +"get_move: prepared_result.legacy_state ?? state."
  6. Changed12 schema fields changed
    • removedInput schema / properties / asset_url
      Removed value: -{
-  "description": "Optional confirmed live URL of the shipped asset.",
-  "type": "string"
-}
    • addedInput schema / properties / attempt_id
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / completion_kind
      Added value: +{
+  "enum": [
+    "prepared_result",
+    "independent_work"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / expected_legacy_state
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / expected_legacy_updated_at
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / expected_move_state
      Added value: +{
+  "description": "Required with expected_move_updated_at for independent_work.",
+  "enum": [
+    "pending",
+    "taken_on",
+    "shipped",
+    "skipped",
+    "archived",
+    "expired",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / expected_move_updated_at
      Added value: +{
+  "description": "Required with expected_move_state for independent_work.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / founder_confirmed
      Added value: +{
+  "const": true,
+  "type": "boolean"
+}
    • addedInput schema / properties / job_id
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / note
      Added value: +{
+  "maxLength": 2000,
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / published_url
      Added value: +{
+  "description": "The actual public URL, when the completed task has one. This is distinct from a prepared asset.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedInput schema / required
      Previous value: -[
-  "move_id"
-]New value: +[
+  "move_id",
+  "completion_kind",
+  "job_id",
+  "attempt_id",
+  "founder_confirmed"
+]
  7. Changed2 schema fields changed
    • changedInput schema / properties / asset_url / description
      Previous value: -"Optional confirmed live URL of the shipped marketing asset."New value: +"Optional confirmed live URL of the shipped asset."
    • changedInput schema / properties / move_id / description
      Previous value: -"The growth move id (uuid), from list_feed."New value: +"Move id (uuid), from list_feed."
  8. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds valuable context beyond the schema: it requires the 'act' scope, is free, and critically never publishes. It does not explain what mutation/destruction the destructiveHint implies (e.g., state transition effects), so it stops short of full disclosure.

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?

Five dense sentences, each earning its place, with the critical precondition (founder confirmation) and the never-publishes correction front-loaded. No filler.

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 13-parameter mutation with no output schema, the description covers purpose, preconditions, routing, URL rules, scope, and cost. It omits what the move's resulting state becomes and how this relates to undo_move, but the sibling set covers reversal, so the gap is minor.

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 85%, so the baseline is 3. The description adds conditional semantics not in the schema: completion_kind mapping (prepared_result after review vs independent_work for separate work) and the URL rule (live published_url to ship, planned_url stays prepared). That lifts it above baseline.

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 and resource ('Record completion') and immediately corrects the misleading name by clarifying 'This records an attestation; it never publishes anything.' This distinguishes it cleanly from siblings like review_move, accept_move, and skip_move.

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?

Explicitly conditions use on founder confirmation ('only after the founder explicitly confirms it') and routes between the two completion_kind values with named conditions. It also states the alternative condition for site changes (live published_url vs planned_url). Nothing is left to inference.

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

All AfterLaunch toolsInspect
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.

Resources