Skip to main content
Glama
Sign In
Sunstone Weave: Local Semantic Code Search

Sunstone Weave: Local Semantic Code Search

by space-bacon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Forget a woven folder

weave_forget
DestructiveIdempotent

Delete a folder's index from your local machine without removing the folder's own files. Use this to stop indexing a specific directory or free up disk space.

Instructions

Delete a folder's index from this machine. The folder's own files are not touched.

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": {
      "path": "<path>"
    },
    "name": "weave_forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe woven folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is partly covered. The description adds genuinely useful context beyond that: what is destroyed (the index) and what is explicitly preserved (the folder's files), which softens the otherwise alarming destructive hint. It does not discuss reversibility or how the index can be rebuilt.

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, front-loaded with the action and followed by the critical scope limitation. No filler.

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 one-parameter, no-output tool whose annotations carry the safety profile, the description covers the essentials. The only real gap is behavior on non-woven folders and whether the index can be regenerated, which matters given the destructive hint.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'path' as the woven folder. The description adds no format, path-shape, or example beyond the schema, 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 gives a specific verb and resource — deleting a folder's index — and immediately disambiguates 'forget' from file deletion with 'the folder's own files are not touched.' It is clear on its own, though it does not explicitly contrast itself with siblings like weave_folder or weave_list.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of the sibling tools. The intended usage (removing a folder from the index) is only inferable from the purpose sentence.

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