Skip to main content
Glama
Sign In
ChannelTerm

ChannelTerm

by akira-init1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Download Diagnostic Archive

terminal_read_diagnostic
Read-only

Read diagnostic ZIP archive bytes by diagnostic ID and archive offset as base64 to download and verify exported diagnostics before expiry.

Instructions

Read up to 65536 ZIP bytes by diagnostic_id and archive byte offset as base64. This offset is not a Session cursor. Download before expiry/eviction; verify the exported SHA256.

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": {
      "diagnostic_id": "<diagnostic_id>",
      "offset": "<offset>"
    },
    "name": "terminal_read_diagnostic"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetYes
max_bytesNo1..65536; default 65536.
diagnostic_idYes

Output Schema

NameRequiredDescriptionDefault
eofYes
dataYes
nextYes
sizeYes
sha256Yes
encodingYes
bytes_readYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavior: archives are time-limited and can be evicted, content is base64-encoded, and integrity should be checked against the exported SHA256. It leaves out what happens at end-of-archive or after eviction, and why idempotentHint=false despite a byte-addressable read.

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?

Two short sentences, zero filler, with the core read semantics front-loaded and the operational caveats (expiry, SHA256 verification) trailing in a single compact clause.

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 an output schema present, return-value detail is not needed, and the description covers the essentials for a chunked read. The remaining gap is how an agent knows it has reached the end of the archive or should retry after eviction.

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?

Schema coverage is only 33% (only max_bytes has a schema description), so the description must compensate. It does: it defines offset as an archive byte offset explicitly not a session cursor, ties diagnostic_id to the archive, and restates the 65536 upper bound that governs max_bytes.

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+resource+unit: read ZIP bytes of a diagnostic archive by diagnostic_id and byte offset, returned as base64. That is precise enough to distinguish it from terminal_export_diagnostics (creation) and from cursor-based reads, though it never names those siblings 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 real usage context: call before the archive expires or is evicted, and verify the exported SHA256 afterward. The clause 'This offset is not a Session cursor' pre-empts the most likely misuse (confusing it with terminal_read/terminal_wait cursor semantics). It does not say whether terminal_export_diagnostics must run first.

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