Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Propose a growth move

propose_move
Destructive

Add a pending move to your user's growth moves. WHEN: your user asks for it or their standing orders call for it, and no move covers the work yet, such as a thread on a community they work, a placement ask, outreach, a directory listing or a page for their site. A repeat (same kind and target, or kind and title) hands back the existing move id. It comes back with its posture: a Reddit or Hacker News target is draft_only, meaning you draft and your user posts, and you never post there yourself without their yes in your thread. Outreach goes from their address, never without their yes. Free; 'act' scope; a fixed number a day. WHAT COMES BACK: the move id and posture.

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": {
      "title": "<title>",
      "why": "<why>",
      "kind": "<kind>"
    },
    "name": "propose_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyYesWhy it is worth their time, in one or two sentences.
kindYescommunity_answer or community_reply: a thread. earned_media or citation_outreach: a placement ask. long_form_content: a page on their site.
draftNoOptional: your draft.
titleYesThe move, as your user would name it.
servesNoOptional: the plan channel this serves.
targetNohttps address; required for a thread, directory or cited page.
sourcesNoOptional: up to five https addresses behind the why.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / draft / description
      Previous value: -"Optional: your drafted reply."New value: +"Optional: your draft."
    • changedInput schema / properties / kind / description
      Previous value: -"community_answer for a question thread; otherwise community_reply."New value: +"community_answer or community_reply: a thread. earned_media or citation_outreach: a placement ask. long_form_content: a page on their site."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "community_reply",
-  "community_answer"
-]New value: +[
+  "community_reply",
+  "community_answer",
+  "directory_listing",
+  "citation_outreach",
+  "earned_media",
+  "cold_outreach",
+  "long_form_content"
+]
    • addedInput schema / properties / serves
      Added value: +{
+  "description": "Optional: the plan channel this serves.",
+  "enum": [
+    "linkedin",
+    "site",
+    "placements",
+    "x",
+    "reddit",
+    "quora",
+    "youtube",
+    "outreach",
+    "other"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / target / description
      Previous value: -"The https address of the thread itself."New value: +"https address; required for a thread, directory or cited page."
    • changedInput schema / properties / title / description
      Previous value: -"The thread, as the founder would name it."New value: +"The move, as your user would name it."
    • changedInput schema / required
      Previous value: -[
-  "title",
-  "why",
-  "kind",
-  "target"
-]New value: +[
+  "title",
+  "why",
+  "kind"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare write/destructive/closed-world; the description goes well beyond by disclosing idempotent repeat behavior, the returned posture field, the draft_only rule for Reddit and Hacker News targets, the requirement of user consent before posting or outreach, and operating constraints ('Free; act scope; a fixed number a day'). That is exactly the mutation consequence and rate-limit context the annotations cannot convey.

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?

Front-loaded with the action, then WHEN and WHAT COMES BACK as labeled sections, which is easy to scan. It is dense and slightly awkward in places ('without their yes in your thread', repeated consent phrasing), but nearly every sentence carries operational weight.

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?

With no output schema, the description compensates by stating the return ('the move id and posture'). Combined with cost, scope, daily limit, dedupe behavior, and the consent/drafting rules, an agent has everything needed to invoke this correctly on a 7-parameter mutation tool.

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; the description earns a step up by revealing semantics the schema lacks — that identity is determined by 'same kind and target, or kind and title', and that posture is derived from the target (Reddit/HN implies draft_only). It does not, however, expand on why, sources, or serves beyond what the schema says.

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?

Opens with a specific verb and resource: 'Add a pending move to your user's growth moves.' The 'pending' qualifier plus the examples of covered work (community thread, placement ask, outreach, directory listing, site page) make it distinguishable from siblings like accept_move, revise_move, or ship_move without opening their schemas.

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?

An explicit WHEN clause gates usage ('your user asks for it or their standing orders call for it, and no move covers the work yet'), which is precisely the condition separating this from revise_move. It also states the dedupe rule ('A repeat ... hands back the existing move id'), so the agent knows a re-proposal is safe rather than an error.

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