Skip to main content
Glama
Sign In
turbocontext

turbocontext

by e-x-h-i-b-i-t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clear_workspace

Removes all indexed code chunks, stored memories, and file hashes from a workspace to reset its indexing state.

Instructions

Purges all indexed code chunks, stored memories, and file hashes for workspace_id from storage.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "clear_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool purges data, which implies destructive behavior, but does not disclose reversibility, required permissions, or any safety mechanisms. The specifics of what is purged are listed, but deeper behavioral context is missing.

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 a single, concise sentence that efficiently conveys the tool's action and scope. No unnecessary words or information.

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

Completeness2/5

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

Despite having an output schema (not shown), the description provides no context about return values or side effects. For a destructive tool with minimal additional info (no annotations), this leaves gaps in understanding what happens after the operation.

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?

The input schema has 0% description coverage, meaning no parameter descriptions. The description does not elaborate on the 'workspace_id' parameter beyond its name, so it adds no semantic value beyond the schema. Given the low coverage, this is a significant gap.

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 uses a specific verb 'Purges' and clearly lists the resources (indexed code chunks, stored memories, file hashes) that are affected. It distinguishes itself from sibling tools like index_workspace (which indexes) and search_code (which searches), making its purpose unique and clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to use or not use this tool. No alternatives or prerequisites are mentioned. The description lacks context about when this operation is appropriate or what conditions should be met before calling it.

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