Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

mark_whatsapp_message_read

Idempotent

Send a read receipt for an inbound WhatsApp message — the blue ticks the contact sees. Takes the wamid from the whatsapp.event.received webhook that delivered the message, plus connection_id or number_id naming the number it arrived on (Sautikit stores no messages, so the wamid alone does not identify the number).

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": {
      "wamid": "<wamid>"
    },
    "name": "mark_whatsapp_message_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
wamidYesMeta message id of the INBOUND message to acknowledge, taken from the whatsapp.event.received webhook that delivered it
purposeNoRequired on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
number_idNoSautikit number id (a UUID from list_numbers) the message arrived on; mutually exclusive with connection_id
connection_idNoUUID of the WhatsApp connection the message arrived on; mutually exclusive with number_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish idempotency, non-destructiveness and closed-world scope, so the description needn't restate safety. It adds real behavioral context the annotations don't carry: that Sautikit stores no messages, so the wamid alone cannot identify the number — explaining why a second identifier is required. It does not describe failure modes (invalid wamid, stale receipt), keeping it at 4.

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, front-loaded with the action and its visible effect, followed by the exact sourcing constraint for the identifiers. The parenthetical is load-bearing rather than decorative; nothing could be cut without losing information.

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 single-required-parameter acknowledgement tool with no output schema, the description covers the action, the prerequisite source of the id, and why the optional identifiers exist. Only minor gaps remain: what the tool returns and how it behaves on an already-read or unknown message.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds rationale beyond the schema: wamid must be the INBOUND message id sourced from the webhook, and the number/connection identifier is needed because the message isn't retained server-side. That explains intent rather than just repeating field definitions.

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?

States a specific verb and resource ("Send a read receipt for an inbound WhatsApp message") and disambiguates with the observable effect ("the blue ticks the contact sees"). That clearly separates it from send_whatsapp_message and send_whatsapp_typing without the agent needing to open a schema.

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?

Gives the concrete trigger: it applies to inbound messages whose wamid came from the whatsapp.event.received webhook. It does not explicitly name alternatives or state when not to use it (e.g. for outbound messages or already-read threads), so it stops short of full when/when-not guidance.

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

All Sautikit 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