Skip to main content
Glama

m9k_unignore_project

Idempotent

Remove a project from the ignore list to resume indexing in future sessions. Previously purged sessions require re-indexation separately.

Instructions

Remove a project from the ignore list. Future sessions will be indexed again. Previously purged sessions are NOT restored (requires backfill re-indexation).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesProject path to unignore

Implementation Reference

  • The MCP tool registration and handler implementation for 'm9k_unignore_project'.
    server.registerTool(
      'm9k_unignore_project',
      {
        description:
          'Remove a project from the ignore list. Future sessions will be indexed again. ' +
          'Previously purged sessions are NOT restored (requires backfill re-indexation).',
        inputSchema: {
          project: z.string().describe('Project path to unignore'),
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false,
        },
      },
      async ({ project }) => {
        unignoreProject(ctx.db, project);
    
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify({
                unignored: true,
                project,
              }),
            },
          ],
        };
      },
    );
  • Database helper function that removes a project from the ignore list.
    export function unignoreProject(db: Database.Database, project: string): void {
      db.prepare('DELETE FROM ignored_projects WHERE project = ?').run(project);
    }
Behavior4/5

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

Adds crucial lifecycle context beyond annotations: explicitly states that previously purged sessions are not restored and notes the backfill requirement. This complements the annotations (idempotentHint: true, destructiveHint: false) by explaining actual data consequences rather than just safety properties.

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: action (sentence 1), positive effect (sentence 2), critical limitation/caveat (sentence 3). Information is front-loaded and each sentence 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?

For a single-parameter configuration tool with no output schema, the description adequately covers the operation, immediate effects, and important historical data caveats. Annotations cover safety properties, leaving the description to focus on functional semantics.

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 description coverage, the schema fully documents the 'project' parameter. The description implies the parameter refers to a project path but doesn't add semantic details (e.g., format, whether absolute/relative) beyond what the schema already provides.

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?

States specific action ('Remove a project from the ignore list'), identifies the target resource, and distinguishes function from sibling m9k_ignore_project through the 'unignore' context. The second sentence clarifies the outcome ('Future sessions will be indexed again').

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

Usage Guidelines4/5

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

Provides clear behavioral context about what happens when used (future indexing resumes) and critical limitations (previously purged sessions NOT restored). While it doesn't explicitly name m9k_ignore_project as the inverse operation, the effects imply when to use it versus alternatives.

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