Skip to main content
Glama
Sign In
alga-psa-mcp

alga-psa-mcp

Official
by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alga_tickets_comments_list

Read-only

Retrieve comments on a ticket, including internal notes marked by is_internal, and paginate long threads with limit and offset.

Instructions

List comments on a ticket. Internal notes are included for internal users; each comment's is_internal flag says which. Use limit (up to 200) and offset to read long threads in parts.

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": {
      "id": "<id>"
    },
    "name": "alga_tickets_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
orderNo
offsetNo
content_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is free to add real value — and it does, disclosing that internal notes appear only for internal users and that each comment carries an is_internal flag. That is a permission-dependent visibility caveat an agent could not infer from the schema, though return shape and default ordering remain unstated.

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

Conciseness5/5

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

Three short sentences, front-loaded with the operation, then the internal-note caveat, then pagination. No filler and no restatement of the tool name.

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?

For a read-only list tool with no output schema, the description covers the essentials: what is listed, the visibility caveat, and how to page. The gap is the undocumented content_format and order semantics, which matters since both are enums.

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%, so the description must carry the parameter burden and it only partially does. It explains limit's ceiling (200) and offset's pagination purpose, but says nothing about the required id's format, the order enum, or the full-vs-markdown content_format enum, leaving two of five parameters entirely undocumented.

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?

States a specific verb and resource ("List comments on a ticket") with the scope narrowed to a single ticket id. It is unambiguous against the sibling set, which contains no other comments-listing tool, though the description never names a sibling to route away from.

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

Usage Guidelines3/5

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

Guidance is implied: use it when you already have a ticket id and want its thread, and use limit/offset for long threads. There is no explicit statement of when not to use it, nor any named alternative such as alga_tickets_get or alga_tickets_search for the parent ticket.

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