Skip to main content
Glama
Sign In

VivaDialog

by com.vivadialog
OverviewDiscussionsAdmin

List contacts

list_contacts
Read-onlyIdempotent

List the people who wrote to the workspace, most recent first, with their stage. Search by name or handle.

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

Input Schema

NameRequiredDescriptionDefault
qNo
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.
stageNo

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds the sort order (most recent first) and that a stage accompanies each contact, but says nothing about pagination behavior or result caps beyond what the schema already documents.

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?

Two short sentences, front-loaded with what is listed and ordered before the search hint. No filler, though the search hint reads as an afterthought rather than a structured parameter note.

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 simple read-only list tool with documented pagination in the schema, the description covers purpose, ordering and query semantics adequately. The missing piece is explicit stage filtering, but the enum makes it discoverable.

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 50%: page and limit are documented in the schema, while q and stage are bare. The description partly compensates by clarifying that q searches 'name or handle', but never explains that stage filters the list to the enumerated stages (new/lead/customer/lost).

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 description gives a specific verb and resource and even defines the domain ('the people who wrote to the workspace'), plus ordering ('most recent first') and the returned field ('with their stage'). It distinguishes the tool from list_members/list_segments only implicitly, since those siblings are never named.

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?

'Search by name or handle' implies when the q parameter is useful, but there is no guidance about when to use this tool rather than list_members, list_segments, or list_conversations. Usage is inferable from the name but not 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