Skip to main content
Glama
Sign In

AfterLaunch

by io.afterlaunch
OverviewDiscussionsAdmin

Pick up a job

pick_up_job
Destructive

Use this to claim a queued job before you work on it. Pass job_id and attempt_id exactly as the queue row shows them, null included. Start work only when the response says claim_won:true; any other result means another agent holds it, so do not start. 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": {
      "job_id": "<job_id>",
      "attempt_id": "<attempt_id>"
    },
    "name": "pick_up_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id (uuid), from list_queue.
attempt_idYesExact attempt id from list_queue; null only for a stored legacy job.
session_urlNoOptional. The launch already gave your user the link to this session; pass it only when you opened this session yourself and can see its address.
site_repositoryNoOptional, for a routine working a site move: the repository it can write to, as owner/name, or null if it has none. Omit it to say nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / site_repository
      Added value: +{
+  "description": "Optional, for a routine working a site move: the repository it can write to, as owner/name, or null if it has none. Omit it to say nothing.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / session_url / description
      Previous value: -"Your own session URL, if you have one, so the founder can open where the work is happening."New value: +"Optional. The launch already gave your user the link to this session; pass it only when you opened this session yourself and can see its address."
  3. Changed2 schema fields changed
    • addedInput schema / properties / attempt_id
      Added value: +{
+  "description": "Exact attempt id from list_queue; null only for a stored legacy job.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedInput schema / required
      Previous value: -[
-  "job_id"
-]New value: +[
+  "job_id",
+  "attempt_id"
+]
  4. Changed1 schema field changed
    • addedInput schema / properties / session_url
      Added value: +{
+  "description": "Your own session URL, if you have one, so the founder can open where the work is happening.",
+  "type": "string"
+}
  5. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds real context beyond the annotations: the concurrency model (another agent may hold the claim), the decisive response field claim_won, the cost ('Free'), and the required 'act' scope. It does not explain what is destroyed despite destructiveHint=true, leaving that annotation unexplained.

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?

Three short sentences, front-loaded with purpose, then the pass-through rule, then the success condition and scope. No wasted wording.

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 explaining the one response field an agent must branch on (claim_won) and the exclusivity semantics. Optional parameters are left to a fully documented schema, which is appropriate.

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 meaningful guidance that the schema does not: pass job_id and attempt_id exactly as the queue row shows them, null included.

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 ('claim a queued job') and its temporal condition ('before you work on it'), which clearly separates it from siblings like report_job or get_claims.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit usage context and a strong exclusion: start work only when the response says claim_won:true, otherwise do not start. It does not name an alternative tool for the losing case, but the when/when-not guidance is unambiguous.

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