Skip to main content
Glama

List persisted task history after a bridge restart (read-only, bounded)

dsh_list_history
Read-onlyIdempotent

Lists read-only summaries of tasks recorded by earlier bridge processes so you can inspect persisted history without resuming, continuing, canceling, or restarting any runtime.

Instructions

Read-only view of tasks recorded under the configured DATA_ROOT/tasks by earlier bridge processes. Returns at most limit (default 20, hard maximum 100) projected summaries. Every response fixes source=persisted-history, runtimeAttached=false, runtimeAlive=null, canContinue=false and canCancel=false. The recorded state, timestamps and PID are evidence only; this tool never probes, resumes, continues, cancels or restarts a recorded runtime, and never recaptures a workspace. One corrupt entry is reported without hiding valid entries.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum summaries to return. Default 20, maximum 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.8

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and non-destructive, and the description goes further by fixing the response contract (source=persisted-history, runtimeAttached=false, runtimeAlive=null, canContinue=false, canCancel=false), plus corrupt-entry handling and the cap on results.

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 scope and read-only guarantee are front-loaded, and each following sentence adds a distinct fact — bounds, fixed response fields, corrupt-entry resilience — with no filler or hedging.

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 no output schema, the description compensates by describing the projected summaries, the fixed response flags, and graceful handling of corrupt entries, which is everything needed to call and interpret this single-parameter read 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 100% and the single limit parameter is already documented with its bounds in the schema; the description's mention of default 20 and hard maximum 100 restates that rather than adding new meaning, so the baseline 3 applies.

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 the specific verb (list) and the exact resource (task records persisted under DATA_ROOT/tasks by earlier bridge processes), and the read-only framing separates it from live-runtime siblings such as dsh_get_task or dsh_continue_task without needing the 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?

Makes the selection condition explicit — use this only to inspect records left by prior bridge processes — and enumerates what it will never do (probe, resume, continue, cancel, restart, recapture), which implicitly routes those intents to the recovery/control siblings, though no sibling is named outright.

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