Skip to main content
Glama

ui_archive_project

Archive or unarchive a project by ID in the app-only work-plan interface to hide inactive work or restore it when needed.

Instructions

App-only: archive or unarchive a project.

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_id": "<project_id>"
    },
    "name": "ui_archive_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
archivedNo
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a mutation tool. It never states whether the operation requires elevated permissions, whether archiving is reversible, what happens to a project's tasks/conversations when archived, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler, which is structurally clean. However, the brevity comes at the cost of under-specification rather than efficient density, so it only earns a middle score.

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

Completeness1/5

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

A mutation tool with no annotations, no output schema, and 0% parameter documentation needs the description to cover permission requirements, reversibility, and default boolean behavior. None of that is present, leaving the agent unable to call it safely beyond guessing from the parameter names.

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?

Schema description coverage is 0%, so both parameters rely on the description. The phrase 'archive or unarchive' implies the `archived` boolean selects direction, which is useful, but it never says what omitting `archived` does (default behavior) and gives no meaning for `project_id` (ID format, validity).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb pair (archive or unarchive) and a specific resource (project), so the agent knows the operation. It does not distinguish this from siblings like ui_update_project or ui_delete_project, and 'App-only' is unexplained, so it stops short of a 5.

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

Usage Guidelines2/5

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

No guidance on when to choose archiving versus deleting (ui_delete_project) or updating (ui_update_project). The only routing hint is the cryptic 'App-only' qualifier, which does not tell an agent the conditions under which this tool is callable versus alternatives.

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