FeatureOS

List comments

list_comments

Read-only

List comments on a feature request with pagination and optional date filtering.

Returns a paginated list of comments for the specified feature request. Each comment includes the author, body text, and timestamps. Use date filters to narrow results to a specific time window.

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": {
      "feature_request_id": "<feature_request_id>"
    },
    "name": "list_comments"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1).
`to_date`	No	Only return comments created on or before this date (YYYY-MM-DD).
`per_page`	No	Number of comments per page, max 50 (default: 20).
`from_date`	No	Only return comments created on or after this date (YYYY-MM-DD).
`feature_request_id`	Yes	The ID of the feature request whose comments to list.

Output Schema

Name	Required	Description	Default
`page`	No
`comments`	No
`has_more`	No
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds that results are paginated and contain author, body, and timestamps. It does not add permissions, rate-limit, ordering, or pagination-metadata details beyond the schema and output schema.

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 short and front-loaded, though the second sentence largely restates the pagination/feature-request scope from the first. The remaining sentences add useful return and filtering context without excessive length.

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?

With full schema coverage, annotations, and an output schema, the definition contains enough context to call the tool correctly. Minor omissions such as sort order or pagination metadata are either schema-covered or unnecessary for 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?

Schema description coverage is 100%, so all five parameters are already documented in the schema. The description reinforces feature_request_id, pagination, and date filtering but adds no syntax or constraints beyond 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?

The description names a specific verb (List) and resource (comments) and scopes it to a feature request, which clearly separates it from singular get_comment and create/update_comment siblings. Pagination and date filtering are front-loaded.

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?

It gives context for listing comments and a tip to use date filters to narrow results, but it never states when to choose this over get_comment or other list/search tools, nor any exclusions. Usage is implied rather than explicitly routed.

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

All FeatureOS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.