Skip to main content
Glama
Sign In
Waggle-mcp

Waggle-mcp

by Abhigyan-Shekhar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clear_project

Delete all memory data for a project/repository, including nodes, transcripts, repos, context windows, and connected edges. Requires confirm=true to execute.

Instructions

Delete all memory data for one project/repository, including nodes, transcripts, repos, context windows, and connected edges. Requires confirm=true.

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": {
      "project": "<project>"
    },
    "name": "clear_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to perform the destructive clear operation.
dry_runNoPreview the clear operation without deleting data.
projectYesProject/repository scope to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.17

TDQS

A3.8/5.0
Behavior4/5

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

No annotations present, so description covers destructive nature, lists affected data, and explains confirm safety mechanism along with dry_run preview. Could add permission or recovery details.

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?

Two-sentence description is concise and front-loaded with the main action. Could use more structured listing but no wasted words.

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

Completeness3/5

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

Adequately describes destructive operation and safety options, but lacks details on recovery, permissions, or return value. Acceptable given no output schema.

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 covers all parameters with descriptions (100% coverage). Description reiterates confirm requirement and dry_run preview but adds minimal extra meaning beyond schema.

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?

Description clearly states it deletes all memory data for one project/repository, listing specific items (nodes, transcripts, repos, context windows, edges). Scope is distinguished from siblings like clear_all (all projects) and clear_session (session).

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?

Implies usage for clearing a single project given confirm=true, but lacks explicit guidance on when to use versus siblings like clear_all or clear_session. No exclusions or prerequisites mentioned besides confirmation.

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