Skip to main content
Glama
Sign In

VivaDialog

by com.vivadialog
OverviewDiscussionsAdmin

List conversations

list_conversations
Read-onlyIdempotent

Read direct-message conversations in the unified inbox, most recent activity first. senderUnverified true: an email conversation whose sender failed the DMARC check, so the address may be forged; it is not linked to a contact and has no participantName. hasUnverifiedMail true: some email in the conversation failed the DMARC check, also when the customer has written there since; get_messages marks each one with senderUnverified.

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_conversations"
  }
}

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.

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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: sort order and the precise meaning of the senderUnverified and hasUnverifiedMail result flags, including the non-obvious case where hasUnverifiedMail persists after the customer replies.

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?

Purpose and ordering are front-loaded in the first sentence, and the remaining text is two tight flag definitions with no filler. Every clause carries information an agent would otherwise have to guess at without an output schema.

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, explaining the two most easily misread response flags is exactly the right use of the description, and it does so precisely. It stops short of describing the other fields a conversation record carries or what happens on an empty inbox, which leaves a small residual gap for a list tool.

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%, and both page and limit are documented in the schema including defaults, ranges, and the overflow-note behavior. The description adds nothing about the parameters, so the baseline applies.

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 ("Read direct-message conversations in the unified inbox") plus the ordering guarantee ("most recent activity first"). It doesn't compare itself to siblings like list_channels or get_messages, so the boundary between listing conversations and listing channels is left implicit.

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?

Usage is implied by the scope phrase "direct-message conversations in the unified inbox" and by the pointer that "get_messages marks each one with senderUnverified," which hints at a list-then-drill-down flow. However, there is no explicit when-to-use/when-not statement or named alternative for reading non-DM channels.

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