Skip to main content
Glama
Sign In
project-manager

project-manager

by samrullo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pm_delete_task

Deletes a task from the project manager by task ID. Accepts optional user ID. Removes the specified task permanently.

Instructions

DELETE /tasks/{task_id}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "pm_delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
x_user_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations and only the HTTP method as context, the description fails to disclose behavioral traits such as idempotency, side effects, or error conditions. The agent receives minimal insight into the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While very concise, the description is under-specified, containing only a single tautological sentence. It does not earn its place as it provides almost no useful information.

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

Completeness1/5

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

Given the tool has 2 parameters (one required), no nested objects, and an output schema, the description is severely incomplete. It ignores return values, error handling, and any contextual details needed for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description adds no parameter explanations. The two parameters (task_id, x_user_id) are not described, leaving the agent without guidance on their semantics or usage.

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

Purpose3/5

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

The description 'DELETE /tasks/{task_id}' clearly indicates the action and resource, but it is a tautology of the tool name and endpoint, providing no additional semantic clarity. It does not explain the functional purpose, such as 'Permanently removes a task'.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description neither explains when to use this tool versus alternatives (e.g., pm_update_task) nor specifies any prerequisites or context.

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

Deploy Server

Other Tools