Skip to main content
Glama
Sign In
code-index-pg

code-index-pg

by tgt-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_project

Remove a project from the code index, cascading deletion of all its indexed data to maintain a clean and accurate searchable codebase.

Instructions

Remove an indexed project and all its data (cascade).

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": "remove_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose that the action is destructive and cascades to all project data. It does not mention irreversibility, permission requirements, or what happens to dependent index state, which would strengthen transparency for a destructive operation.

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?

The description is one compact, front-loaded sentence that states the action, the resource, and the cascade behavior without filler or redundancy. Every word adds value.

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 low-complexity tool with a single parameter and an output schema, the description covers the essential operation and destructive scope. The only meaningful gap is the lack of guidance for the 'path' parameter, but the overall context is sufficient for basic correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has a single 'path' parameter with no description, and the tool description does not explain what type of path is expected or how it relates to an indexed project. Since schema description coverage is 0%, the description needed to compensate but did not.

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?

The description uses a specific verb ('Remove') and a specific resource ('indexed project') and clarifies the destructive scope ('all its data (cascade)'). This clearly differentiates it from the sibling search/indexing tools.

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?

The intended use is implied by the verb: use this when you want to delete an indexed project. However, there is no explicit statement about when not to use it or which sibling tool might be an alternative, such as update_index for non-destructive changes.

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