Skip to main content
Glama
Sign In

VivaDialog

by com.vivadialog
OverviewDiscussionsAdmin

List comments

list_comments
Read-onlyIdempotent

Read comments in the unified inbox, newest first. Filter by status, platform or channel. Texts longer than 4000 characters are cut (text_truncated, text_length).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
limitNoItems per page, 1 to 100. Default 20. A page too large to return comes back with fewer items and a note saying which limit to keep.
statusNopending = still waiting for an answer.
platformNo
channel_idNoA channel id from list_channels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Items per page, 1 to 100. Default 20."New value: +"Items per page, 1 to 100. Default 20. A page too large to return comes back with fewer items and a note saying which limit to keep."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent, read-only, closed-world operation, so the safety profile is covered. Beyond that the description adds genuinely non-obvious behavior: newest-first ordering and the 4000-character truncation with the text_truncated and text_length fields, which matters because there is no output schema to disclose it. It does not mention pagination totals or how many pages exist, which keeps it below a 5.

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 with no filler: the purpose, the filter dimensions, and the truncation caveat all appear in that order. Nothing could be removed without losing information an agent needs.

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 no output schema, the truncation note is exactly the kind of return-value detail the description must carry, and it does. Pagination is handled well in the schema. What is missing is any indication of whether results report a total count or whether filters are AND-combined, which would matter for a list tool with five optional parameters.

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 coverage is 80%, so page, limit, status and channel_id are already documented in the schema itself. The description's 'filter by status, platform or channel' mostly restates those parameters, though it does usefully signal that the filters combine and that platform is one of the filterable dimensions. The baseline of 3 is appropriate.

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 definition states a specific verb and resource ('Read comments in the unified inbox') plus the ordering ('newest first'), which is enough to distinguish it from a generic messages reader. It stops short of explicitly distinguishing itself from the closest sibling, get_messages, so an agent must infer that this returns public comments rather than direct messages.

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?

The mention of filtering 'by status, platform or channel' implies the filtering use case, but there is no explicit when-to-use statement, no exclusions, and no pointer to alternatives such as get_messages or get_inbox_analytics. Usage is inferable rather than stated.

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

All VivaDialog toolsInspect
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.

Resources