Skip to main content
Glama
Sign In
askmywa

askmywa

by Ruwad-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Chats involving a contact

get_contact_chats
Read-onlyIdempotent

Lists every chat involving a contact, including direct and group chats, ordered by most recent activity and paginated by cursor.

Instructions

List every chat involving a contact: the direct chat and the groups they wrote in, most recently active first. Paginated by cursor.

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": {
      "contact": "<contact>"
    },
    "name": "get_contact_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNopage size (default 20, max 200)
cursorNonext_cursor from the previous page
contactYesphone number, JID or contact name

Output Schema

NameRequiredDescriptionDefault
chatsYes
has_moreYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds real context beyond that: result ordering ('most recently active first'), pagination mode ('paginated by cursor'), and exactly which chats are included. It does not say what happens with archived chats or when a contact is unknown.

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?

Two sentences, zero filler, with the inclusion scope front-loaded before the ordering and pagination details. Every clause carries 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?

An output schema exists, so return value structure need not be explained, and all three parameters are fully documented in the schema. The remaining gap is minor: no statement about ordering ties, archived/empty cases, or what an empty result means.

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% — limit (default 20, max 200), cursor (next_cursor from previous page) and contact (phone number, JID or name) are all documented in the schema. The description adds only that results are cursor-paginated, which the schema's cursor field already conveys, so baseline 3 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 ('List every chat involving a contact') and narrows scope explicitly to the direct chat plus groups the contact wrote in, which implicitly separates it from a direct-chat-only sibling. It stops short of naming any sibling, so the differentiation is inferable rather than stated.

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 sentence — you'd pick this when you want all chats for a contact rather than one chat. There is no explicit when-to-use/when-not guidance, no mention of list_chats or get_direct_chat_by_contact as alternatives, and no prerequisites or edge cases (unknown contact, archived chats).

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