Skip to main content
Glama

remove_project

Delete a project and its tasks from the database, optionally removing the folder from disk if within a safe root directory.

Instructions

Remove a project from Metis entirely.

Deletes project record and associated tasks from DB.
If delete_files=True, also deletes the external_path folder from disk
(only if path is within RC root — safety check enforced).

Args:
    project_id: The project_id to remove.
    delete_files: If True, delete the project folder from disk. Default False.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
delete_filesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries burden. It discloses key behaviors: deletes records and tasks, optionally deletes folder with safety check. However, it does not mention irreversibility, auth requirements, or return value.

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?

Description is very concise with three focused sentences plus Args list. Every sentence earns its place: purpose, deletion scope, and parameter details. No wasted words.

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?

Given moderate complexity, the description covers main behavior and parameters. Output schema exists but not shown; description could mention irreversibility and return value for full completeness.

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

Parameters4/5

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

Schema description coverage is 0%, so description compensates by explaining both parameters: project_id as the ID to remove and delete_files as boolean with default False and safety condition. This adds meaning beyond schema titles, though project_id format is not detailed.

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 clearly states 'Remove a project from Metis entirely' with specific verb and resource. It explains what gets deleted (project record, tasks, optionally folder) and distinguishes from siblings like archive_project which implies temporary state.

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?

The description provides clear context for when to use (permanent removal) and includes a safety check for file deletion. However, it does not explicitly compare to alternatives like archive_project or unarchive_project, which would help the agent decide.

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/SVerITG/Metis_PH'

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