Skip to main content
Glama
BenAHammond

code-auditor-mcp

by BenAHammond

project_tasks

Create, list, update, and delete tasks in a per-project queue. Supports subtasks, status, priority, labels, and blocking dependencies.

Instructions

Manage a persistent per-project task queue. Tasks and analyzer configs survive sync_index reset; reset clears function index, cached audits, code maps, and schema overlays (no ghost code references). Use delete to remove a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoDelete mode: reject (default), detach subtasks, or cascade descendants.
dueAtNoISO 8601 due datetime for create; omit or null in patch to clear.
labelNoFilter/search by label value.
limitNoMax tasks to return for list (default 500, max 1000).
patchNoFor update: partial fields (title, description, status, priority, labels, metadata, parentTaskId, source, blockedBy, dueAt, sortOrder, relatedFiles, relatedSymbols).
queryNoCase-insensitive text search across title/description/labels/files/symbols.
titleNoTask title. Required for create.
actionYeslist | list_tree | create | get | update | complete_task | delete. list/list_tree/create use projectPath or default to process.cwd(); create needs title; get/update/complete_task/delete need taskId; update needs patch object.
labelsNoString tags (e.g. ["audit","refactor"]).
sourceNomanual | audit | mcp. Filter for list; provenance for create; can be set via update patch.
statusNopending | in_progress | blocked | done | cancelled. Filter for list; initial status for create; can be set via update patch.
taskIdNoStable task id (UUID). Required for get, update, complete_task, delete.
metadataNoArbitrary JSON object: related file paths, links, audit IDs, etc.
priorityNoOptional priority for create/update patch.
blockedByNoTask IDs this item is blocked by (waiting-on).
sortOrderNoLower numbers sort first within a project (default 0).
descriptionNoLonger description / notes.
hasChildrenNoFilter tasks that do/do not have direct subtasks.
overdueOnlyNoFilter tasks with dueAt in the past and not closed.
projectPathNoProject root (resolved). Omit to use the MCP server working directory (same default idea as audit path); response includes projectPathDefaulted when omitted.
parentTaskIdNoOptional parent task for subtasks.
relatedFilesNoRepo-relative or absolute file paths tied to the task.
actionableOnlyNoFilter tasks that are open and unblocked by open dependencies.
relatedSymbolsNoFunction, class, or component names for cross-linking.
blockedByTaskIdNoFilter tasks blocked by this task ID.
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses key behaviors (tasks survive reset, what reset clears) but lacks details on side effects of create, update, or list actions. For a tool with 25 parameters and multiple actions, more behavioral context is needed.

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 two sentences, front-loading purpose and key behavior. Every sentence adds value with no redundancy. It's concise and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (25 params, multiple actions, no output schema), the description is incomplete. It doesn't explain return values, task object structure, or details for each action. Significant gaps remain.

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 coverage is 100%, so the baseline is 3. The description adds marginal value by linking 'delete' to the action parameter, but most parameter meaning is already in the schema. The description does not significantly enhance parameter understanding.

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 states the tool manages a persistent per-project task queue, distinguishing it from sibling tools like sync_index. It specifies what survives reset and what is cleared, making the purpose unambiguous.

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 provides a clear usage hint ('Use delete to remove a task') and notes that list/list_tree/create use projectPath or default. However, it does not explicitly differentiate when to use this tool over sibling tools, though the context implies it's for task management.

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/BenAHammond/code-auditor-mcp'

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