Skip to main content
Glama
Sign In
project-manager

project-manager

by samrullo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pm_create_comment

Create a comment on a task. Provide a payload with comment details and optionally a user ID.

Instructions

POST /comments — TaskCommentCreate.

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": {
      "payload": "<payload>"
    },
    "name": "pm_create_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
x_user_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as authentication requirements, side effects, or idempotency. The minimal description fails to inform the agent about 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?

The description is extremely concise but at the cost of being under-specifying. It is more of a label than a helpful description, lacking necessary detail.

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?

Despite having an output schema and nested objects, the description provides no context about return values or payload structure. The tool's complexity demands more explanatory content to be complete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning beyond the schema. Parameters 'payload' (object with additionalProperties true) and 'x_user_id' (optional) are undocumented, leaving the agent with no guidance on required fields or format.

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 'POST /comments — TaskCommentCreate' indicates the tool creates a comment via POST, so purpose is clear. However, it does not differentiate from sibling tools like pm_create_task or pm_create_tag, missing specificity.

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

Usage Guidelines1/5

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

No guidance on when to use this tool vs alternatives like pm_list_comments or pm_update_comment. The description lacks any context for usage.

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