memory-manager-mcp

Get current task

get_current_task

Retrieve the most relevant open task for a project and view other open tasks by providing the workspace path.

Instructions

Returns the most relevant open task for the project, plus other open tasks.

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

Input Schema

Name	Required	Description	Default
`workspacePath`	No	Workspace directory of the project. Defaults to the server working directory.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 17, 2026

TDQS

A3.8/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 full burden. The verb 'Returns' implies a read-only operation, but it does not explicitly state safety, how relevance is determined, or any edge-case behavior. Adds some context about output but lacks depth.

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?

Single sentence with no filler, front-loads the primary action, and is appropriately sized for the tool's simplicity.

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 simple getter with one optional parameter, the description provides a high-level summary of the return value. However, it does not specify the exact data structure (e.g., array vs object) or field details, which is a minor gap given no output schema.

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 description covers the single optional parameter workspacePath with 100% coverage, so the description need not provide parameter details. The description does not mention the parameter, and baseline 3 applies due to high schema coverage.

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?

Description uses specific verb 'Returns' and clearly identifies the resource: 'most relevant open task for the project, plus other open tasks.' This distinguishes it from sibling tools like get_project_context and get_decisions.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies usage for retrieving the current task, but does not mention exclusions or alternative tools, leaving the agent to infer context.

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

Deploy Server