Skip to main content
Glama

backlog_wakeup

Provides a startup briefing with active tasks, constraints, and recent completions to quickly resume work. Optionally scope to a folder or resume a mid-flight operation.

Instructions

Dense session-start briefing: active tasks, current epics, project constraints (requirements as stubs, violated/at-risk first — treat these as standing product intent), recent completions (with evidence snippets), recent activity, and the home-wide unfiled work count. No focal entity required — use this at the start of every session to understand what you were working on. Optional scope narrows the entity sections to a folder, milestone, or epic; unfiled remains home-wide because parentless work has no subtree ancestry. Optional operation resumes a mid-flight operation document: its live state becomes the briefing's FOCUS centerpiece and the rest of the briefing yields budget to it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
homeNoSelect the document home for this read. "all" queries global plus the explicitly supplied/bridged project root; it never scans prior projects.
scopeNoOptional entity ID to scope the briefing to a subtree. Must be a container (folder/milestone/epic). Use a folder ID for project-scoped wake-up (e.g. "FLDR-0001"). Omit to get everything across the whole backlog.
operationNoOptional focal document ID (e.g. "OP-0001") to resume a mid-flight operation: the briefing gains a `focus` centerpiece carrying that document's declared wakeup projection, and non-focal sections yield budget deterministically (completions 5→2, activity 5→2, knowledge 5→3, declared sections capped at 2; constraints never yield). Works for any document whose substrate declares `disclosure.wakeup`. Unknown or non-live IDs error honestly, naming live candidates.
max_activityNoMax recent activity-log entries. Default: 5.
project_rootNoProject root for this call. Overrides the bridge project root and selects the project home.
max_completionsNoMax done tasks in the "recent" section. Default: 5.
max_constraintsNoMax requirement constraint stubs. Default: 3; 0 disables. Truncation is reported via metadata.constraints_omitted.
evidence_snippet_charsNoMax chars of evidence to include per completion. Default: 160.
Behavior4/5

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

Without annotations, the description carries full burden. It discloses key behaviors: return sections (tasks, epics, constraints, completions, activity, unfiled), the operation focus mechanism with budget yielding, truncation via metadata.constraints_omitted, and error handling for unknown operation IDs. It does not cover auth or rate limits, but given the read-only nature this is acceptable.

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?

The description is concise and well-structured, front-loading the purpose in the first sentence. It efficiently organizes sections: main purpose, optional scope, optional operation, with no redundant or wasted phrases. Every sentence adds value.

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?

Given the complexity (8 parameters, no output schema, no annotations), the description provides a solid understanding of the tool's operation. It covers parameter effects and behavior. However, it does not specify the response structure beyond listing sections; a brief example or field names would make it fully complete.

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 baseline is 3. The description adds significant value beyond schema descriptions by explaining usage context: 'No focal entity required', 'unfiled remains home-wide because parentless work has no subtree ancestry', and the operation focus budget reductions. This contextualizes parameters effectively.

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 clearly defines the tool as a 'dense session-start briefing' compiling active tasks, current epics, project constraints, recent completions, recent activity, and unfiled work count. This specific and composite purpose distinguishes it from sibling tools like backlog_search (focused search) or backlog_get (single entity retrieval).

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?

The description explicitly states 'use this at the start of every session to understand what you were working on,' providing clear context. It also explains optional scope and operation parameters, but does not include explicit 'when not to use' or alternatives, which would elevate it to a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gkoreli/backlog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server