Skip to main content
Glama

send_read_receipt

Notify a contact that you have read their messages by sending read receipts for specific timestamps. Use after retrieving messages with get_conversation.

Instructions

Send a read receipt to a contact, notifying them that you have read their messages. The sender sees a 'Read' indicator under their messages in their Signal app. Pass all timestamps you want to mark as read in a single call to batch the receipts. Timestamps come from the received_at or sent_at fields in get_conversation. Note: read receipts are only delivered if the sender has read receipts enabled in their Signal settings. Use after reading a conversation with get_conversation to acknowledge the messages. Do NOT use to mark messages as read in the local store — get_conversation does that automatically. Do NOT use for group messages — Signal does not support per-sender read receipts in groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
senderYesPhone number (E.164) of the contact whose messages you are acknowledging
timestampsYesTimestamps of the messages to mark as read (from get_conversation sent_at/received_at fields)
Behavior4/5

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

Discloses effect ('Read' indicator), batching behavior, source of timestamps, and dependency on sender's settings. However, it does not mention error handling or what happens if receipts are not delivered (e.g., silent failure).

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?

Concise, well-structured with front-loaded purpose. Every sentence adds value, no redundancy.

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?

Covers purpose, usage, batching, restrictions, and prerequisite. Lacks return value description (though likely trivial) and error conditions, but sufficient for a simple notification tool.

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 100%, so description adds limited value. The batching hint ('pass all timestamps in a single call') provides useful context beyond schema, but meaning of timestamps is already clear from schema description.

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 clearly states the verb 'send read receipt' and the resource 'a contact', and distinguishes from sibling tools by explicitly forbidding use for group messages and noting that get_conversation handles local marking.

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

Usage Guidelines5/5

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

Explicit guidance: use after reading a conversation with get_conversation, pass all timestamps in a single call to batch, and do not use for group messages or local store marking. Also notes prerequisite about sender's read receipts setting.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server