Skip to main content
Glama
Sign In
Learn Shell

Learn Shell

by sf-shenfeng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

live_snapshot_get_latest

Fetch the session's current mid-lesson snapshot. This snapshot plus subsequent moves provides the minimal data needed to restore and continue the session.

Instructions

读 session 最近一份 mid-lesson snapshot. compact 恢复时第一步: snapshot + 之后的 moves = 续上 session 的最小集.

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": "live_snapshot_get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It indicates a read operation ('读') and adds context about the recovery workflow, but does not mention error handling, permissions, or the return format. This is adequate but not rich.

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 description is very concise, with two short sentences front-loading the core purpose and a key usage note. Every word earns its place.

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?

For a simple tool with one parameter and no output schema, the description gives the core purpose and a usage context that implies the return value (the snapshot). It leaves a little to be desired about the exact response structure, but is sufficiently complete for its simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. The description only mentions 'session' in passing and does not explain the session_id parameter's meaning or expected value beyond the obvious from the name, providing no additional semantic value.

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?

The description clearly states the action ('读' / read) and the resource ('session 最近一份 mid-lesson snapshot' / the most recent mid-lesson snapshot of a session). It also distinguishes from siblings like live_snapshot_write by focusing on retrieval.

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?

The description provides a clear usage context: it is the first step in compact recovery, with the formula 'snapshot + 之后的 moves' defining its role. It doesn't explicitly list alternatives or exclusions, but the recovery workflow guidance is specific and useful.

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