DevReply

Resolve or reopen

set_status

Idempotent

Resolves a conversation (it leaves the open inbox) or reopens it. Resolving is visible to the user: their chat shows "Marked as resolved" and they may get a push. Only resolve when the team has actually answered.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes	resolved (the user sees "Marked as resolved") or open (reopens it).
`conversation_id`	Yes	The conversation's id (from list_conversations or get_user).

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Its status now: resolved or open.
`changed`	No	Resolving only: false when it was already resolved.
`user_notified`	No	Resolving only: the user was shown "Marked as resolved".
`conversation_id`	Yes	The conversation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 5, 2026

addedInput schema / properties / conversation_id / description

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

addedInput schema / properties / status / description

Added value: +"resolved (the user sees \"Marked as resolved\") or open (reopens it)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "changed": {
+      "description": "Resolving only: false when it was already resolved.",
+      "type": "boolean"
+    },
+    "conversation_id": {
+      "description": "The conversation.",
+      "format": "uuid",
+      "type": "string"
+    },
+    "status": {
+      "description": "Its status now: resolved or open.",
+      "type": "string"
+    },
+    "user_notified": {
+      "description": "Resolving only: the user was shown \"Marked as resolved\".",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "conversation_id",
+    "status"
+  ],
+  "type": "object"
+}

AddedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false. The description adds genuinely new behavioral context: the action is user-visible ('Marked as resolved'), may trigger a push notification, and removes the conversation from the open inbox.

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 short sentences, effect stated first, then user-visible consequence, then the caution. No filler and nothing buried.

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?

An output schema exists, so return values needn't be described. Both parameters are covered by the schema, and the description supplies the side-effect and cautionary context an agent needs before mutating a conversation's status.

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% and the enum values are already documented in the schema, so the description merely restates the resolved/open meaning. Baseline 3 applies since the schema does the heavy lifting for both parameters.

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?

Specific verb (resolve/reopen) plus resource (conversation) and a clarifying effect ('it leaves the open inbox'). This cleanly separates it from sibling mutation tools like set_category, tag_conversation, or reply_to_user.

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 explicit when-to-use guidance ('Only resolve when the team has actually answered') and explains the two states. It does not name a sibling alternative or state when reopening is appropriate, so it stops short of full routing guidance.

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?