Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Propose a growth move

propose_move
Destructive

Add a pending move to your user's growth moves. WHEN: you found a thread on a community they work, or their plan calls for a placement ask, outreach, a directory listing or a page for their site, and no move covers it yet. 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.

Input Schema

TableJSON 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.6/5.0
Behavior4/5

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

The description goes well beyond the annotations: it documents dedup behavior ('a repeat ... hands back the existing move id'), the draft_only posture for Reddit/Hacker News, the requirement of user consent before posting, that outreach sends from the user's address, and that the call is free, needs 'act' scope, and is rate-limited daily. It doesn't state reversibility or failure modes, but the disclosure is rich.

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 core action, then structured by 'WHEN:' and 'WHAT COMES BACK:' labels. It is dense and the WHEN sentence runs long, but nearly every clause carries operational information and nothing is redundant.

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 supplies the return contract ('the move id and posture'), the posture semantics, the cost/scope/rate-limit profile, and the trigger conditions. An agent has everything needed to call this correctly without further lookups.

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; however the description adds meaning the schema doesn't, mapping kind values to behavioral consequences (Reddit/HN targets become draft_only) and clarifying that duplicate detection keys on kind+target or kind+title, which sharpens how 'title' and 'target' are used.

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?

The first sentence names a specific verb and resource with state ('Add a pending move'), which cleanly separates it from sibling mutators like accept_move, ship_move, and archive_move. The agent can tell this creates a proposal rather than acting on an existing one.

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?

The 'WHEN:' clause enumerates concrete triggers (a found community thread, a placement ask, outreach, a directory listing, a page for their site) and pairs them with an explicit exclusion: 'and no move covers it yet.' This is genuine when-to-use and when-not guidance with no inference required.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources