Skip to main content
Glama
DeepSeek Harness MCP Server

DeepSeek Harness MCP Server

dsh_list_tasks

Read-only

Lists tasks retained in the current server process to recover a task_id after an uncertain submit response. Tasks are not persisted across restarts.

Instructions

List tasks retained in this server process. Use to recover a task_id after an uncertain submit response. Tasks are not persisted across MCP server restarts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 safety is covered. The description adds genuinely useful context beyond that: results are process-local and are lost across MCP server restarts. It says nothing about volume, ordering, or whether finished tasks are included.

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?

Three short sentences, each carrying a distinct fact: what it lists, why to call it, and the persistence caveat. The lifecycle warning is placed last where it lands as a constraint rather than burying the purpose.

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?

There is no output schema, so describing the returned task entries (fields, ordering, whether completed tasks appear) would have closed the remaining gap. For a zero-parameter list tool the description is otherwise sufficient to call it correctly and interpret the process-scoped lifetime.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the input schema. Baseline 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?

States a specific verb and resource ("List tasks retained in this server process") and scopes it to the current process. It implicitly separates itself from dsh_get_task by naming the recovery use case, though it never names a sibling explicitly.

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?

Gives a concrete trigger for use: recovering a task_id after an uncertain submit response, which is exactly the ambiguous-post-submit scenario an agent hits. It does not say when not to use it or name get_task/cancel_task as the follow-on alternative, so it stops short of full routing guidance.

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