Skip to main content
Glama
alexd73

PlanfixMCP

by alexd73

add_task_comment

Add a comment to a Planfix task, providing text, attachments, recipient notifications, and scheduling options.

Instructions

Добавить комментарий к задаче

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumber of task
filesNoExisting Planfix files attached to the comment. Each item must contain an existing file id.
ownerNoComment author. Specify an existing employee or contact/company with a prefixed number, for example user:5 or contact:92.
silentNoSilent modefalse
dateTimeNoComment date and time as TimePoint.
isHiddenNoWhether the comment is hidden.
isPinnedNoWhether the comment is pinned.
sourceIdNoUnique identifier of the third-party application or system.
recipientsNoComment notification recipients. Specify employees or contacts in users, existing groups in groups, and roles in roles.
descriptionNoComment text.
sourceObjectIdNoUnique identifier of the specific object in the third-party application or system.
sourceDataVersionNoVersion of the object data in the third-party application or system.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
resultYes
Behavior2/5

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

No annotations are present, so the description carries the full burden. It does not disclose that this is a write operation, any permission requirements, or what the response contains. The presence of an output schema is not leveraged to explain return behavior. Minimal behavioral information is given.

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 description is a single concise sentence with no wasted words. It is efficient but extremely sparse, lacking context that could be added without much verbosity. It earns a 4 for being concise, not for richness.

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?

With 12 parameters, no annotations, and a complex domain (comments, recipients, files, hidden/pinned flags), a one-sentence description is insufficient. It omits context about prerequisites (e.g., existing task), side effects (e.g., notifications), and return values, making it incomplete for effective tool selection.

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?

The schema description coverage is 100%, so all 12 parameters already have descriptions in the structured schema. The tool description adds no additional parameter semantics, warranting the baseline score of 3.

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

Purpose4/5

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

The description cleanly states the action: 'Add a comment to a task' (in Russian). It clearly identifies the verb (add) and resource (task comment), distinguishing it from contact comment tools. However, it does not explicitly differentiate from update_task_comment or other comment operations.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention that the task must already exist, that this is for creating new comments, or that update_task_comment serves for edits. There is no mention of prerequisites or exclusions.

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/alexd73/PlanfixMCP'

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