Skip to main content
Glama
Sign In
dsh-baton

dsh-baton

by JialaoLiu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

dsh_read_session

Read-onlyIdempotent

Retrieve recent session messages—roles, timestamps, text, and called tool names—to catch up before continuing a session. Read-only; returns no tool output.

Instructions

Read the last messages of a session (role, time, text and the names of tools called; no tool output), to catch up before continuing it. Read-only.

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": {
      "session_id": "<session_id>"
    },
    "name": "dsh_read_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastNoHow many of the most recent messages to return; total_messages tells how many there are
session_idYesSession id from dsh_list_sessions, e.g. session-…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.4
    • changedInput schema / properties / last / description
      Previous value: -"How many recent messages"New value: +"How many of the most recent messages to return; total_messages tells how many there are"
    • changedInput schema / properties / session_id / description
      Previous value: -"Session id, e.g. session-…"New value: +"Session id from dsh_list_sessions, e.g. session-…"
  2. First observedv0.5.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' is largely redundant. What the description does add is the return content shape — that tool calls are reported by name but their output is omitted — which is real behavioral context absent from the structured fields.

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 with the payload description front-loaded and the purpose clause second. No filler, and the 'no tool output' caveat is placed where it will be read.

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, the description correctly carries the burden of describing returns and does so at field level. Minor gaps remain: it doesn't mention total_messages (only the schema does), pagination/truncation behavior when `last` exceeds available messages, or what happens with an invalid session_id.

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%: `last` documents its default and semantics, and `session_id` documents its source (dsh_list_sessions) and format. The description adds no parameter-level meaning beyond the schema, 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 a specific verb and resource ('Read the last messages of a session') plus the exact fields returned (role, time, text, tool names) and an explicit exclusion (no tool output). An agent can tell this apart from dsh_send, dsh_answer, and dsh_list_sessions without opening any 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?

'to catch up before continuing it' gives a concrete usage context that implicitly routes the agent here before dsh_send/dsh_answer. It does not explicitly name sibling alternatives or state when not to use it (e.g. versus dsh_list_sessions for discovery), 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.

Deploy Server

Other Tools