Skip to main content
Glama
Sign In
BoteX

BoteX

by kubainter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

read_scratchpad

Retrieve the full execution or terminal log saved in the scratchpad by memory ID, so you can inspect offloaded output and diagnose run details.

Instructions

Reads the full execution or terminal log offloaded to the scratchpad (.botex/scratchpad/<memory_id>.log).

Args:
    memory_id: The ID of the scratchpad entry (e.g. 'mem_exec_a1b2c3d4').
    workspace_dir: Workspace root directory. Empty = engine.default_workspace
           from the config, else the server's current directory.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "read_scratchpad"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYes
workspace_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the log is offloaded to a specific file path and explains the workspace_dir fallback behavior, but it does not mention error conditions, permissions, truncation, or whether reads are safe/non-destructive.

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?

The description is front-loaded with the core purpose and then provides a compact Args block. It is efficient overall, though the Args section partially duplicates what the schema could carry.

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?

An output schema exists, so return values need not be explained. The two input parameters are documented with useful semantics, and the description is sufficient for an agent to invoke the tool correctly despite the lack of annotations and sibling routing guidance.

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 description coverage is 0%, so the description must compensate. It does document both parameters, including an example memory_id format and the fallback semantics for an empty workspace_dir, which meaningfully extends the bare schema.

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?

The description states a specific verb and resource: it reads the full execution or terminal log from a scratchpad log file. It also gives the concrete file location pattern, which distinguishes it from generic memory tools. However, it does not explicitly differentiate itself from sibling tools such as read_memory.

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?

Usage is implied by the resource description: use this to retrieve offloaded execution or terminal logs. There is no explicit guidance on when to use this rather than read_memory or search_memory, and no exclusions or prerequisites are stated.

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