Skip to main content
Glama

pick_up

Resume an in-progress project build by retrieving the previous session's hand-over—ticket, working doc, notes, files, and checklist—while safely managing session takeover.

Instructions

Pick the build up where an earlier session stopped. Call it first when you are told to work on a project and a ticket is already in progress (list_tickets says so), or when told to pick up. Returns the hand-over: the ticket with its working doc, what the previous session said last and the files it touched, the builders' notes and a checklist. It takes the build over (the previous session is marked replaced) unless that session may still be open: then it says so and does nothing; ask the person, and call again with take_over=true only if they say so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pick_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo
take_overNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description describes its behavior in detail: it takes the build over, marks the previous session as replaced, and when that session may still be open it does nothing and reports back rather than acting. It also enumerates what the hand-over returns (ticket, working doc, last message, files touched, builder notes, checklist), which is unusually complete.

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?

The action and its trigger are front-loaded in the first clause, and every sentence adds behavioral information. It runs long as a single dense paragraph, and the return-value list is arguably redundant given an output schema exists.

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 two-parameter tool with an output schema, this covers the risky path (concurrent sessions, replacement, confirmation flow) that an agent most needs to know. The only real omission is what the `project` argument does and how omission is resolved.

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 0%, so the description must carry both parameters. It explains take_over precisely (only set it after the person confirms), but leaves `project` undefined: it does not state whether it is required, what the empty default means, or what happens when it is omitted. The take_over semantics are strong; the project gap keeps it below a 5.

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 description uses a specific verb and resource: "Pick the build up where an earlier session stopped," and immediately explains the trigger condition (a ticket already in progress, per list_tickets). An agent can distinguish this from siblings like get_ticket or hand_over without opening any schema.

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?

It names explicit call conditions: "Call it first when you are told to work on a project and a ticket is already in progress (list_tickets says so), or when told to pick up." It also states when to escalate (ask the person) and the exact condition for retrying with take_over=true, leaving little to inference.

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