Skip to main content
Glama
Sign In
Whatify MCP Server

Whatify MCP Server

by ashusingh1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

whatify_list_conversations

List inbox conversations from your WhatsApp account, with optional filters for status and page size.

Instructions

List inbox conversations.

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": "whatify_list_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoe.g. open, closed
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description should disclose behaviors like pagination, filtering, or potential rate limits. It only states the basic action, failing to provide needed behavioral context.

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

Conciseness3/5

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

The description is a single concise sentence, but it is overly brief given the tool has two parameters and no output schema. It could include more information without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is incomplete for a tool with two parameters and no output schema. It does not explain pagination (implied by 'per_page'), filtering options for 'status', or the nature of the response list.

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?

The schema description coverage is only 50% (only 'status' has a partial description). The tool description does not add any meaning for parameters, such as the expected format for 'status' or the role of 'per_page' in pagination.

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 clearly states the verb 'List' and the resource 'inbox conversations', distinguishing it from sibling list tools like 'whatify_list_campaigns' and 'whatify_list_contacts'. However, the term 'inbox' is ambiguous without additional context.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, such as when to filter by status or how pagination works. The description lacks any usage context.

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