Skip to main content
Glama
Sign In
dsh-any-agent

dsh-any-agent

by xmtlzzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Manage queue

dsh_queue
Destructive

Inspect or change a conversation's pending task queue: list queued tasks, cancel one, rewrite queued text, or promote one to the front. The queue is memory-only and lost on restart.

Instructions

Inspect or change a conversation's queue of pending tasks (it only manages tasks already queued; enqueue with dsh_send(queue=true); memory-only, lost on restart). action=list lists them; remove cancels one and writes a cancelled sentinel; update rewrites the queued text; promote moves one to the front.

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>",
      "action": "<action>"
    },
    "name": "dsh_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe new text, for update.
actionYes
run_idNoRequired for remove / update / promote.
conversation_idYesConversation id, from dsh_start or dsh_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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."
    • changedInput schema / properties / run_id / description
      Previous value: -"remove / update / promote 必填"New value: +"Required for remove / update / promote."
    • changedInput schema / properties / text / description
      Previous value: -"update 时的新文本"New value: +"The new text, for update."
  2. Addedv0.5.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false and idempotent=false, and the description adds genuinely new context: the queue is memory-only and lost on restart, remove writes a cancelled sentinel, and promote reorders to the front. It does not cover what happens when removing a task that is already running or what list returns, but the side-effect disclosure is well above the annotation baseline.

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?

One dense, front-loaded passage with no filler; the scope constraint and sibling routing come first, followed by per-action semantics. The semicolon-chained action clauses and mid-sentence parenthetical are slightly compressed but still parseable.

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 four-parameter mutation tool with no output schema, the definition covers scope, alternatives, storage lifetime, and per-action effects. The main remaining gap is that list's return shape is never described, which matters because there is no output schema to fall back on.

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 75%, so most parameters are already documented, including run_id's applicability and text's use for update. The description still adds value the schema lacks: it explains the semantics of each action enum value (list lists, remove cancels, update rewrites text, promote moves to front), which the bare enum does not convey.

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 pair and resource: 'Inspect or change a conversation's queue of pending tasks'. It also draws the boundary against the closest sibling by naming dsh_send(queue=true) as the enqueue path, so an agent can distinguish queue management from message sending without inspecting schemas.

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?

Explicitly states the exclusion ('it only manages tasks already queued') and routes the out-of-scope case to the alternative ('enqueue with dsh_send(queue=true)'). Each action's purpose is spelled out, so selecting list vs remove vs update vs promote requires no inference.

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

Deploy Server

Other Tools