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

dsh-any-agent

by xmtlzzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Approval inbox

dsh_inbox
Read-onlyIdempotent

List every pending approval across all conversations, with conversation, tool, reason, command summary and wait time, so you can decide what to allow or deny next.

Instructions

Inbox of pending approvals across conversations (dsh_status covers a single one). Lists every approval waiting for your decision: conversation id and title, approval id, tool, reason, a summary of the command or path, and how long it has waited. Decide with dsh_approval_decide. Returns an empty list when nothing is pending.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dsh_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_inputNoWhether to include a summary of the operation's input (default true).
conversation_idNoOnly this conversation (omit for all).

Output Schema

NameRequiredDescriptionDefault
countYes
approvalsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.8
    • changedInput schema / properties / conversation_id / description
      Previous value: -"只看某个会话（省略 = 全部）"New value: +"Only this conversation (omit for all)."
    • changedInput schema / properties / include_input / description
      Previous value: -"是否带操作输入摘要（默认 true）"New value: +"Whether to include a summary of the operation's input (default true)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "approvals": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "count",
+    "approvals"
+  ],
+  "type": "object"
+}
  2. Addedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the exact fields returned (conversation id/title, approval id, tool, reason, input summary, wait duration) and the empty-list outcome when nothing is pending.

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?

The bolded scope statement is front-loaded, followed by the returned fields, the decision tool, and the empty-result case in a tight sequence. Every sentence carries distinct information with no redundancy.

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?

With an output schema present, the description needn't document return shape, yet it summarizes the key fields helpfully. For a two-optional-parameter, read-only listing tool, nothing an agent needs to call 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?

Schema description coverage is 100%, so both parameters are already documented in the schema, making 3 the baseline. The description reinforces the 'across conversations' default but adds no syntax or format detail, and never mentions include_input.

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 opens with a specific verb+resource, 'Inbox of pending approvals across conversations', and immediately scopes it against dsh_status ('covers a single one'). An agent can distinguish this cross-conversation listing from the single-conversation sibling without opening either schema.

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?

It names the sibling dsh_status and its narrower scope, and routes the follow-up action to dsh_approval_decide, which is clear context for when this tool is the right entry point. It stops short of stating explicit when-not-to-use conditions, but the scoping contrast does most of that work.

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