list_ticketcommentsThe comment thread of a ticket submission, oldest first. Each comment carries app_url, an INTERNAL deep link to the ticket's task drawer — do not hand it to the customer; use the ticket's public_url (from retrieve_ticketsubmissions) for a customer-facing link.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint and idempotentHint true, so the safety profile is covered. The description adds useful behavioral context: the comments are returned oldest first, and each comment contains an internal deep link that should not be shared with customers, pointing to public_url for customer-facing use. This goes beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the main purpose, and every word earns its place. The caution about app_url is concise and necessary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a straightforward list tool with one parameter and rich annotations, the description is mostly complete. It explains the ordering, the content of each comment, and a critical security caveat. It doesn't outline the return format, but no output schema is provided, and the title implies a list.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not mention the submission_id parameter or explain its format/role beyond referring to 'a ticket submission.' With schema description coverage at 0%, the description fails to compensate, though the schema itself does describe the parameter as 'ID of the ticket submission.'
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states that the tool returns the comment thread of a ticket submission, ordered oldest first. This is a clear enough purpose, though it doesn't explicitly use the verb 'list' or differentiate from retrieve_ticketcomments beyond implying a collection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool versus alternatives like list_taskcomments or retrieve_ticketcomments. The only usage-related note is about not sharing app_url with customers, which is more of a behavioral warning than a selection guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly scoped to a specific resource and action, but a few near-overlapping pairs (e.g., list_attachments vs list_taskattachments, create_tasktags vs add_tag_tasks) could cause misselection without close reading. Descriptions are detailed enough to resolve most ambiguity.
The dominant verb_noun CRUD pattern (create_, list_, retrieve_, update_, partial_update_, destroy_) is consistent and predictable. However, non-standard pluralizations (companys, resumeentrys, taskdependencys) and a handful of irregular names (task_assign_user, move_relate_to_tasks) introduce minor inconsistencies.
With 83 tools, this server is far beyond a well-scoped MCP surface, even for a feature-complete project management suite. The sheer volume will overwhelm agents and make selection inefficient, clearly falling into the extreme-mismatch range.
The toolset provides thorough lifecycle coverage across companies, projects, tasks, sprints, attachments, comments, dependencies, tags, reminders, resume entries, tickets, and users. Missing operations like company deletion or task-attachment creation appear intentional and are worked around via existing tools.