Skip to main content
Glama

Read a DSH task

dsh_get

Retrieve a DSH session's current state and last assistant output without waiting, enabling progress checks or result retrieval for a submitted task.

Instructions

Read the current state and last assistant output of a DSH session without waiting.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "dsh_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesDSH session id, e.g. session-… returned by a previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the non-blocking behavior and the return content (current state plus last assistant output), which is more than a bare restatement. It is silent on edge cases such as a missing or expired session, error conditions, or whether the call is strictly side-effect free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One compact sentence with the key qualifier ("without waiting") placed at the end for emphasis. Nothing is redundant, though the brevity comes at the cost of the behavioral detail a no-annotation tool would benefit from.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no annotations and no output schema, the description covers purpose, non-blocking semantics, and what is returned. It does not describe failure behavior for invalid or finished sessions, which leaves a meaningful gap for an unannotated 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?

There is a single parameter with 100% schema description coverage, and the schema already explains the sessionId format. The description reinforces that the id refers to a DSH session but adds no syntax or sourcing detail beyond what the schema states, which is the baseline case.

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?

Specific verb plus resource: "Read the current state and last assistant output of a DSH session." The phrase "without waiting" implicitly sets it apart from dsh_wait, though it does not differentiate it from dsh_info or dsh_sessions. An agent can still tell what it does without opening 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 Guidelines3/5

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

The phrase "without waiting" implies this is the non-blocking polling option, which suggests when to prefer it over a blocking wait tool. However, no alternative is named and there are no explicit when-not conditions or prerequisites, so usage is implied rather than stated.

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