Skip to main content
Glama
Sign In
dsh-mcp-worker

dsh-mcp-worker

by tongsh6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

查询审计日志

dsh_audit
Read-only

Retrieve recent audit events for task lifecycle and approval decisions to trace activity and troubleshoot execution issues.

Instructions

读取最近的审计事件（任务创建/开始/结束/取消、审批决定等），用于追溯与排障。

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_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo返回最近多少条，默认 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds scope value by listing which event types appear and that only recent events are returned, but it says nothing about ordering, retention window, or volume, and no output schema exists to explain the returned record shape.

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?

One compact sentence that front-loads the verb and resource, then the event coverage, then the purpose. Every clause earns its place with no redundant restatement of the title.

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 one-optional-parameter read-only tool with annotations and full schema coverage, the definition is nearly sufficient: the agent knows what it reads and why. The remaining gaps are minor — no mention of recency ordering or that results are capped at 200 — which is acceptable at this complexity.

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 a single optional parameter with 100% schema description coverage ('返回最近多少条，默认 50'), so the schema already carries the meaning. The description adds nothing about the limit — no interaction with ordering or the 200 maximum — so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb (读取) plus a specific resource (审计事件) and even enumerates the event categories covered (任务创建/开始/结束/取消、审批决定). This makes it clearly distinct from the run/status/result siblings, though it does not explicitly name a sibling it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an implied usage context — 用于追溯与排障 (tracing and troubleshooting) — which tells the agent the scenario, but it offers no explicit when-not guidance or comparison to alternatives such as dsh_tasks or dsh_status when the goal is task history.

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