DevReply

Watch a conversation live

watch_conversation

Read-only

Get new messages in a conversation the moment they arrive, instead of re-reading it: returns a URL that streams them (Server-Sent Events). Run the returned command in the background (e.g. Claude Code's background Bash or Monitor, which wakes you on each line): every new message (the user's, the team's, notes, button answers) comes as one data: JSON line, shaped like a get_conversation message; : ping lines every 30 s just keep it open. The loop in command reconnects on its own and resumes after the last message it saw. It ends when the conversation is resolved (an end event) or after 24 h. Use it while you're actively working a conversation with the user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`conversation_id`	Yes	The conversation's id (from list_conversations or get_user).

Output Schema

TableJSON Schema

Name	Required	Description
`how`	Yes	How to use it.
`url`	Yes	The Server-Sent Events stream of its new messages (valid 24 h, reusable).
`command`	Yes	A shell loop to run in the background: streams, reconnects and resumes on its own.
`expires_at`	Yes	When the URL stops working.
`conversation_id`	Yes	The conversation watched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / conversation_id / description

Added value: +"The conversation's id (from list_conversations or get_user)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "command": {
+      "description": "A shell loop to run in the background: streams, reconnects and resumes on its own.",
+      "type": "string"
+    },
+    "conversation_id": {
+      "description": "The conversation watched.",
+      "format": "uuid",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "When the URL stops working.",
+      "format": "date-time",
+      "type": "string"
+    },
+    "how": {
+      "description": "How to use it.",
+      "type": "string"
+    },
+    "url": {
+      "description": "The Server-Sent Events stream of its new messages (valid 24 h, reusable).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "conversation_id",
+    "url",
+    "command",
+    "expires_at",
+    "how"
+  ],
+  "type": "object"
+}

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say readOnlyHint/openWorldHint; the description adds substantial behavior beyond them: SSE `data:` lines shaped like get_conversation messages, `: ping` keep-alives every 30s, automatic reconnect/resume, and termination on resolution (`end` event) or after 24h. This is exactly the operational context an agent needs to run a background stream safely.

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

Conciseness4/5

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

Well front-loaded: the core purpose (stream new messages via an SSE URL) leads, followed by execution details. It is a dense single paragraph rather than over-long, and each clause carries real information, though it could be broken into shorter sentences for scanability.

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?

Given the streaming/background-execution complexity, the description covers how to run it, message format, keep-alives, reconnection, and termination. Even though an output schema exists, the added lifecycle detail is appropriate, and nothing needed 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?

With one parameter at 100% schema description coverage, the schema already documents `conversation_id` and its source (list_conversations/get_user). The description adds no additional parameter syntax or constraints, so the baseline 3 applies.

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+resource (watch/stream new messages in a conversation) and precisely what it returns: a URL that streams messages plus a `command` to run. It implicitly distinguishes itself from the re-reading siblings by framing itself as an alternative to re-reading the conversation.

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 a clear when-to-use condition: 'Use it while you're actively working a conversation with the user,' and contrasts with re-reading, which points to get_conversation. It does not explicitly name get_conversation as the alternative or state when not to use it (e.g. for one-off history reads), so it stops short of a full 5.

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

All DevReply tools Inspect

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

Need Help?