Skip to main content
Glama

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Record output outcome

set_output_status
Destructive

Resolve one drafted marketing output in the founder's review queue: action 'ship' marks it done or posted WITHOUT publishing anywhere, action 'skip' dismisses it. WHEN: call 'ship' the moment the founder confirms the content is actually out, with their go and never on your own; call 'skip' when they decide against it. Posting is the human's decision; reporting the outcome is yours, and it is not optional, because an unreported result leaves the record blind to what the work earned. Report only what is true: a draft you have written is not a draft that went out. This never posts to a channel: real publishing is a separate, human-approved egress step. Free; requires the 'act' scope and Founder tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes'ship' resolves it as done / posted without publishing; 'skip' dismisses it.
output_idYesOutput id (uuid), from list_outputs.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / output_id / description
      Previous value: -"The drafted output id (uuid), from list_outputs."New value: +"Output id (uuid), from list_outputs."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true/readOnlyHint=false; the description adds real behavioral context beyond that: it never posts to a channel, publishing is a separate human-approved egress step, it is free, and it requires the 'act' scope and Founder tier. It also warns against reporting a draft that did not actually go out. No conflict with the destructive annotation, which is consistent with dismissing/settling a queue record.

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 purpose followed by a WHEN block is a good structure, and every part is relevant. There is mild redundancy, though: the no-publishing guarantee is stated twice and the 'not optional' motivation is a second sentence of exhortation rather than new operational information.

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 3-param, two-action resolution tool with no output schema, the description covers everything an agent needs: what each action resolves, when to call each, that it does not publish, the permission prerequisites, and the accuracy constraint on final_text. Nothing material 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 would be 3, but the description meaningfully reinforces 'final_text': only the words actually posted, never a rewrite or the draft, used solely to learn voice, and omittable when unknown. That adds intent and edge-case guidance (do not fabricate the posted text) beyond the schema's field text.

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: resolving one drafted marketing output in the founder's review queue, with the two concrete actions ('ship', 'skip') and what each does. It is clearly distinguishable from near-neighbors like ship_move/skip_move (moves) and from publishing tools, since it explicitly says resolution does not publish.

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?

Gives an explicit WHEN block: call 'ship' the moment the founder confirms content is out, with their go and never on your own; call 'skip' when they decide against it. It also separates the agent's job (reporting) from the human's (posting), so the agent knows this is not an alternative to a real publishing step.

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