Skip to main content
Glama

m9k_ignore_project

Destructive

Exclude a project from conversation indexing in Melchizedek's persistent memory. Prevent future indexing and optionally delete existing indexed sessions for that project.

Instructions

Exclude a project from indexing. Future sessions won't be indexed. Optionally purge existing indexed sessions for this project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesProject path to ignore (e.g. /Users/foo/my-secret-repo)
purgeNoAlso delete already-indexed sessions for this project

Implementation Reference

  • Registration and handler for the m9k_ignore_project tool. It calls ignoreProject from db.js to update the project ignore status and optionally purges project data using purgeProjectData.
    server.registerTool(
      'm9k_ignore_project',
      {
        description:
          "Exclude a project from indexing. Future sessions won't be indexed. " +
          'Optionally purge existing indexed sessions for this project.',
        inputSchema: {
          project: z.string().describe('Project path to ignore (e.g. /Users/foo/my-secret-repo)'),
          purge: z
            .boolean()
            .default(false)
            .describe('Also delete already-indexed sessions for this project'),
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: false,
          openWorldHint: false,
        },
      },
      async ({ project, purge }) => {
        ignoreProject(ctx.db, project);
    
        let sessionsPurged = 0;
        let chunksPurged = 0;
    
        if (purge) {
          const result = purgeProjectData(ctx.db, project);
          sessionsPurged = result.sessionsPurged;
          chunksPurged = result.chunksPurged;
        }
    
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify({
                ignored: true,
                project,
                purged: purge,
                sessionsPurged,
                chunksPurged,
              }),
            },
          ],
        };
      },
    );
Behavior4/5

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

Adds valuable behavioral context beyond annotations: discloses that effects persist across future sessions and specifically describes what gets destroyed when purge=true (existing indexed sessions). Annotations only flag destructive=true without explaining the scope of destruction or persistence implications.

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?

Three sentences with zero waste: front-loaded action ('Exclude'), followed by persistence guarantee ('Future sessions'), and optional destructive detail ('Optionally purge'). Every clause earns its place.

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?

Adequately covers the tool's dual behavior (future exclusion + optional purge) given simple 2-parameter schema and destructive annotations. Minor gap: could mention reversibility via m9k_unignore_project or success indicators, but acceptable without 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?

With 100% schema coverage, description reinforces parameter meanings ('purge existing indexed sessions' aligns with purge boolean) but doesn't add syntax, format constraints, or semantic details beyond what the schema already documents.

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 uses specific verb 'Exclude' with resource 'project' and domain 'indexing', clearly distinguishing it from session-level tools like m9k_delete_session. It clarifies scope (project-level) and persistence (future sessions).

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 context (excluding projects from indexing) and explains the purge option's effect, but lacks explicit when-to-use guidance or comparison to siblings like m9k_unignore_project (reversal) or m9k_delete_session (session-level deletion).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/louis49/melchizedek'

If you have feedback or need assistance with the MCP directory API, please join our Discord server