Skip to main content
Glama
Sign In
code-explorer

code-explorer

by vmikhailov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

clear_workspace_index

Clears indexed data from the workspace database, optionally for a specific subpath or the entire workspace, to remove stale index entries before re-indexing.

Instructions

Clear indexed data from the workspace database.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_workspace_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional subpath to clear, or omit for entire workspace.
workspacePathNoOptional workspace root path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.80.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a destructive operation. "Clear" implies removal, but it does not state whether the deletion is irreversible, whether source files on disk are affected or only the index, whether it requires specific permissions, or what the response looks like.

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?

A single sentence with no filler, and the action is front-loaded. It is efficient, though its brevity is partly why behavioral gaps remain.

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?

For a destructive, zero-annotation tool with no output schema, the description should say more about scope of deletion, reversibility, and post-clear state. What is present covers only the bare action, leaving the agent without the information needed to call it safely.

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% and both parameters already document their meaning, including that path is an optional subpath and that omitting it clears the whole workspace. The description adds no further meaning beyond what the schema provides, so the baseline 3 applies.

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 ("Clear indexed data from the workspace database"), so an agent knows it removes index entries. It does not distinguish itself from siblings such as scan_workspace or init_workspace that likely rebuild or populate that index, and "indexed data" is left somewhat vague.

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 guidance on when to call this versus alternatives, no statement of prerequisites (e.g. whether the workspace must be initialized first), and no mention of the typical follow-up such as re-scanning or re-ingesting. The agent must infer all usage context.

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