Skip to main content
Glama

Get current tasks

taskhold_get_current
Read-only

Get the task in progress (in this project when you pass project), with its steps and the next one to do. Call this at the start of a session. Returns the most recently active in-progress task, its numbered steps with ids (with descriptions and the summaries of done steps), the next step's id, project notes and the latest 3 notes (taskhold_get shows 10); with nothing in progress (or an unknown project) it says so and names taskhold_begin and taskhold_next.

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

Input Schema

NameRequiredDescriptionDefault
projectNoProject name, e.g. the repo folder ("api-server"). Any case, or an id. Unknown names match nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project / description
      Previous value: -"Project name, e.g. the repo folder (\"api-server\"). Matched case-insensitively (or a project id). An unknown name matches nothing."New value: +"Project name, e.g. the repo folder (\"api-server\"). Any case, or an id. Unknown names match nothing."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds substantial context on top: which task is returned ('most recently active in-progress'), what the payload contains (numbered steps with ids, descriptions, summaries of done steps, next step id, project notes, latest 3 notes), and how the empty or unknown-project case is handled. This is behavior an agent cannot get from the annotations.

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 purpose and the call-at-session-start guidance are front-loaded, and the return payload is enumerated compactly in one sentence. It is dense but nearly every clause carries information; the parenthetical note comparison is the only slightly awkward insertion.

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 single optional-parameter, read-only tool with no output schema, the description covers purpose, timing, return contents, and the empty/unknown-project path. Nothing an agent needs to call it correctly 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 is 3, but the description adds meaning beyond the schema: passing project narrows scope to that project, and an unknown project yields an explicit 'says so' response rather than an error or empty list. That consequence is not stated in the schema, which only says 'Unknown names match nothing.'

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 opens with a specific verb and resource ('Get the task in progress ... with its steps and the next one to do') and scopes it by project. It also differentiates itself from sibling taskhold_get by noting the note count ('the latest 3 notes (taskhold_get shows 10)'), so an agent can distinguish the two without opening a 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 gives an explicit invocation point ('Call this at the start of a session') and routes the empty case to named alternatives ('it says so and names taskhold_begin and taskhold_next'). Both the when-to-use and the fallback path are stated rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources