Skip to main content
Glama

Conversation status

dsh_status
Read-onlyIdempotent

Reads live conversation state from server memory without spawning a DSH process, returning status, current tool, output size, latest run status, pending approvals, queue length, and write-lock holder.

Instructions

A lightweight snapshot of one conversation: reads live state from this server's memory without spawning a DSH process. Returns state (running/idle/detached), the current tool and output size while running, the latest turn's run_id, status and review status, pending approvals, queue length, and the write-lock holder lock_holder (when you hit the lock, use it to choose between dsh_takeover and asking the other side to dsh_release). For a turn's full result use dsh_get, for live output dsh_read, for all conversations dsh_list.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "dsh_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesConversation id, from dsh_start or dsh_list.

Output Schema

NameRequiredDescriptionDefault
runNo
busyNo
aliveNo
stateYes
turnsNo
reviewNo
conversation_idYes
pending_approvalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.8
    • changedInput schema / properties / conversation_id / description
      Previous value: -"会话 id,来自 dsh_start 或 dsh_list。"New value: +"Conversation id, from dsh_start or dsh_list."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "alive": {
      +      "type": "boolean"
      +    },
      +    "busy": {
      +      "type": "boolean"
      +    },
      +    "conversation_id": {
      +      "type": "string"
      +    },
      +    "pending_approvals": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "review": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "run": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "state": {
      +      "enum": [
      +        "running",
      +        "idle",
      +        "detached"
      +      ],
      +      "type": "string"
      +    },
      +    "turns": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "conversation_id",
      +    "state"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint. The description adds useful context beyond them: it reads from server memory 'without spawning a DSH process,' which implies low cost and no side effects. It also explains that lock_holder signals a contention path and what that means operationally.

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?

The description is dense and front-loads the core purpose. However, the long enumeration of returned fields partially overlaps with the output schema, which is a minor redundancy. Overall it is well structured and efficient.

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?

Given a single-parameter tool with an output schema, the definition is nearly complete: purpose, cost, behavioral traits, and alternative routing are all covered. The only redundancy is restating return values already captured by the output schema.

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?

There is one required parameter, and schema_description_coverage is 100%; the schema already says it comes from dsh_start or dsh_list. The description adds no format or validation detail beyond that. Baseline 3 is appropriate.

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 states a specific verb and resource: 'A lightweight snapshot of one conversation: reads live state from this server's memory'. It immediately distinguishes itself from the other DSH tools by naming them and their purposes.

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?

The description explicitly routes the agent to alternatives: 'For a turn's full result use dsh_get, for live output dsh_read, for all conversations dsh_list.' It also gives conditional guidance for lock_holder, pointing to dsh_takeover or dsh_release.

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