Skip to main content
Glama

task_context

Show your claimed tasks, handoffs, ready next work, blocked and waiting items scoped to the current folder's project, or get a per-project overview with all_projects.

Instructions

Start here. Working view for this folder's project: your claims, handoffs for you, tasks other operators hold, NEXT ready work, blocked, waiting on owner. Scope comes from the session folder; pass all_projects for a per-project overview.

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": "task_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoSession folder (absolute path). Filled in by the OpenCode plugin; other clients pass the working folder.
jobNoOverride: job (e.g. acme). Normally derived from the session folder.
repoNoOverride: repo within the job. Normally derived from the session folder.
limitNo
projectNoOverride: exact project job.repo.
all_projectsNoCross-project view. Only for explicit global review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that scope is derived from the session folder and that all_projects switches to a cross-project view, but it never states that this is a read-only operation, whether the limit parameter paginates or truncates the sections, or what the response shape per section looks like.

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 imperative "Start here." followed by a compact section enumeration and the scoping rule. Dense but every clause conveys content the agent needs; no filler.

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?

With no output schema, the description does the necessary work of listing the returned categories, and it explains scope derivation for a 6-parameter tool. The remaining gap is limit/pagination behavior, which matters given the capped integer parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the schema already documents cwd, job, repo, project, and all_projects. The description reinforces the session-folder default and the all_projects override but adds nothing about limit (max 20), its truncation semantics, or the precedence between the override parameters and the folder-derived scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource and enumerates what the view contains (claims, handoffs, tasks others hold, NEXT ready work, blocked, waiting on owner), so an agent knows it returns a composite working dashboard rather than a raw list. It does not explicitly contrast itself with sibling task_list/task_get, so sibling differentiation is left to inference.

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?

"Start here" establishes this as the entry-point tool, and the all_projects clause defines the one alternate mode of use. It stops short of stating when to prefer task_list or task_get instead, so alternatives are implied rather than spelled out.

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