Skip to main content
Glama

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

create_comment

Post a comment on a task, project, issue OR client company (exactly one parent). Useful for AI-generated status updates, follow-ups, or notes - including progress on an Issue you filed. Caller must have visibility into the parent project. Task comments support two threads: the focused human-agent thread (threadKind 'AGENT', the task's [Agent] tab) and the team thread (threadKind 'general', the [Comments] tab). Comments default to the team thread, including your own progress/status updates. Set threadKind 'AGENT' ONLY to reply in the focused [Agent] thread - i.e. when replying to a comment you read (via get_task / list_comments / list_related_tasks) whose threadKind is 'AGENT', echo that value so the directed conversation stays in one thread.

Input Schema

NameRequiredDescriptionDefault
taskIdNoComment on a task. Exactly one of taskId/projectId/issueId.
contentYes1-5000 chars. Plain text is formatted: blank lines separate paragraphs, lines starting "- " or "* " become a bulleted list, lines starting "1. " a numbered list.
issueIdNoComment on an Issue (Issue Log). Exactly one of taskId/projectId/issueId/companyId.
companyIdNoComment on a client company (Onplana Services). Exactly one of taskId/projectId/issueId/companyId.
projectIdNoComment on a project. Exactly one of taskId/projectId/issueId.
threadKindNoTask comments only. 'AGENT' = the focused human-agent thread ([Agent] tab); 'general' = the team thread ([Comments] tab). Defaults to the team thread; set 'AGENT' only to reply in the focused human-agent thread.
idempotencyKeyNoOptional idempotency key. Pass a stable unique value (e.g. a UUID) to make this create safe to retry: calling again with the same key within 24h - even from a new session after a reconnect - replays the original result and creates no duplicate. Org-scoped; works across conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / companyId
      Added value: +{
+  "description": "Comment on a client company (Onplana Services). Exactly one of taskId/projectId/issueId/companyId.",
+  "type": "string"
+}
    • changedInput schema / properties / content / description
      Previous value: -"1-5000 chars."New value: +"1-5000 chars. Plain text is formatted: blank lines separate paragraphs, lines starting \"- \" or \"* \" become a bulleted list, lines starting \"1. \" a numbered list."
    • changedInput schema / properties / issueId / description
      Previous value: -"Comment on an Issue (Issue Log). Exactly one of taskId/projectId/issueId."New value: +"Comment on an Issue (Issue Log). Exactly one of taskId/projectId/issueId/companyId."
    • addedInput schema / properties / threadKind
      Added value: +{
+  "description": "Task comments only. 'AGENT' = the focused human-agent thread ([Agent] tab); 'general' = the team thread ([Comments] tab). Defaults to the team thread; set 'AGENT' only to reply in the focused human-agent thread.",
+  "enum": [
+    "AGENT",
+    "general"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds real context beyond the annotations: an authorization prerequisite ('Caller must have visibility into the parent project'), the default routing behavior (comments land in the team thread, including the agent's own status updates), and the directed-conversation pattern for replying. Annotations already cover the safe/non-destructive profile, so the remaining gap is minor.

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?

Front-loads the what, then the routing rules, so the highest-value information is read first. The final sentence is long and parenthetical-heavy, but each clause carries a distinct rule rather than padding.

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?

Covers parent selection, content formatting expectations, thread routing, and the visibility prerequisite for a 7-parameter create tool with no output schema. The only uncovered area, retry/idempotency semantics, is handled adequately by the schema's own parameter description.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3, but the description goes further by explaining the operational intent behind threadKind ('[Agent] tab' vs '[Comments] tab') and by warning that the parameter applies to task comments only. The idempotencyKey parameter is left entirely to the schema.

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?

States a specific verb ('Post a comment') and enumerates the four supported parent resources, with the exactly-one-parent constraint up front. An agent can immediately distinguish this from edit_comment and list_comments without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('AI-generated status updates, follow-ups, or notes - including progress on an Issue you filed') and a precise when/when-not for threadKind: default to the team thread, and set 'AGENT' ONLY when echoing a threadKind you read back from get_task/list_comments/list_related_tasks. It even names the read tools that supply that value.

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

All Onplana toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources