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

dsh-mcp-worker

by tongsh6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

获取批量任务结果

dsh_batch_result
Read-only

Retrieve final outputs, errors, and durations for each task in a submitted batch; long outputs are truncated at a configurable character limit, with full content available via read-result tool.

Instructions

返回批量中每个任务的最终输出/错误/耗时；单条输出超过 max_output_chars 会截断（完整内容用 dsh_read_result）。

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": {
      "batch_id": "<batch_id>"
    },
    "name": "dsh_batch_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYesdsh_batch_run 返回的 batch_id
max_output_charsNo单条输出最大字符数，默认 4000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real behavioral detail on top: per-task error and duration are included, and outputs are truncated at max_output_chars rather than returned whole. It does not state behavior for incomplete or still-running batches, which is a remaining gap.

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?

A single compact sentence front-loads what is returned, then appends the truncation caveat and the fallback tool. No filler, no restatement of the tool name or 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?

With no output schema present, the description carries the return-shape burden and does name the per-task fields (output/error/duration) plus truncation behavior. Missing is whether results include tasks that have not finished, which matters for a batch-result tool.

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 already 100%, and the schema itself documents both max_output_chars (default 4000, max 100000) and batch_id's origin. The description contributes only the consequence of exceeding the limit (truncation) and the follow-up tool, so it does not meaningfully exceed the schema baseline.

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?

Uses a specific verb+resource (返回批量中每个任务的最终输出/错误/耗时) and enumerates the returned artifacts per task, which distinguishes it from dsh_batch_status. It routes to dsh_read_result for full content, but does not explicitly contrast itself with dsh_result, which remains inferable only from the batch naming.

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?

Implies the trigger condition (retrieving final per-task outcomes of a batch) and gives one explicit routing rule: if output exceeds max_output_chars it is truncated and dsh_read_result should be used for the full content. No explicit when-not guidance beyond that single alternative.

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