Skip to main content
Glama

Blue ticks on incoming WhatsApp messages

dosai_set_whatsapp_read_marks
Destructive

Choose whether the bot marks clients' WhatsApp messages as read (blue ticks). mark_read=false keeps them unread, so the owner's phone keeps showing notifications for chats the bot handles; true is the default. Only for a number connected by QR or pairing code. Requires admin or owner role.

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": {
      "project_id": "<project_id>",
      "mark_read": "<mark_read>"
    },
    "name": "dosai_set_whatsapp_read_marks"
  }
}

Input Schema

NameRequiredDescriptionDefault
mark_readYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes beyond them by spelling out the concrete consequence of mark_read=false (the owner's phone keeps showing notifications for chats the bot handles) and by stating the default is true. That is genuine behavioral context an agent cannot read off the schema, though it never explains why the operation is flagged destructive or what happens to already-read messages.

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?

Three tight sentences ordered as: what it does, what each value means, then eligibility constraints. No boilerplate, no repetition of the title, and the most decision-relevant fact (the false-case consequence) is placed early.

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

Completeness5/5

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

A two-parameter boolean setter with no output schema needs exactly this much: the effect of each value, the default, connectivity scope, and required role. Nothing an agent needs in order to invoke it correctly is missing.

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%: project_id is documented in-schema ('From dosai_list_projects'), while mark_read has no schema description at all. The description fully compensates for mark_read by explaining both boolean states and the default, but adds nothing about project_id, so it is better than baseline without being complete.

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

Purpose5/5

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

The description opens with a specific verb and resource: choosing whether the bot marks clients' WhatsApp messages as read (blue ticks). The parenthetical '(blue ticks)' anchors the vague term 'read' to an observable UI effect, so an agent knows exactly what setting is being flipped.

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

Usage Guidelines4/5

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

It gives real preconditions: only for a number connected by QR or pairing code, and it requires admin or owner role. What it does not do is name a sibling setting tool as the alternative when the agent actually wants notification routing or template behavior, so it stops short of full when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources