Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

chat_getClassInfo

Get chat details for a WhatsApp session using session ID and optionally chat ID. Returns chat object for further interaction.

Instructions

[Chat] Get the chat

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": {
      "sessionId": "<sessionId>"
    },
    "name": "chat_getClassInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdNoUnique WhatsApp ID for the given chat (either group or personal)
sessionIdYesUnique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations, the description must fully disclose behavior. 'Get the chat' reveals nothing about whether this is read-only, what kind of data is returned, or any side effects. It fails to provide any behavioral context beyond a trivial getter.

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

Conciseness2/5

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

The description is under-specified rather than concise. A single vague phrase 'Get the chat' does not earn its place; it lacks necessary detail and is effectively a placeholder.

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

Completeness1/5

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

For a tool with no output schema, no annotations, and a vague name, the description provides almost no context. It is completely inadequate for an agent to understand what 'class info' means or how this differs from similar getters.

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?

The schema already documents both parameters with descriptions and examples (100% coverage). The description adds no parameter semantics or additional meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Get the chat', which is a clear verb+resource but too vague—it doesn't mention that this is specifically about class info (as the name implies) and could apply to any chat getter. This does not distinguish it from sibling tools like client_getChatById or chat_getContact.

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

Usage Guidelines1/5

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

No guidance is provided about when to use this tool versus the many other chat-related getters. There is no mention of alternatives, prerequisites, or context. The description gives no usage context at all.

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