Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Archive project

archive_project
Destructive

Archive a project by setting confirm=true to move it out of active use while retaining its records for later reference.

Instructions

Archive a project. Requires confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
project_idYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write. The description adds one genuinely useful behavioral fact beyond the annotations: that a confirm=true flag is mandatory, i.e. an explicit confirmation gate. It says nothing about what archiving actually does — whether it is reversible, whether data or fielding is affected, 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.

Conciseness4/5

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

Two short sentences, front-loaded with the action, with zero filler. It is efficient but so terse that the second sentence carries information that belongs in a fuller behavior statement.

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

Completeness2/5

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

This is a destructive mutation with no output schema and no annotation coverage of consequences. An agent about to call it still cannot tell whether archiving is reversible, what gets hidden versus deleted, or whether in-flight fielding is impacted — critical information that only the description could supply.

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?

Schema coverage is 33%; organization is documented in the schema and project_id is self-evidently the target. The description does compensate for the undocumented confirm parameter by stating it must be true, which is meaning the schema does not provide. That is meaningful but thin for a three-parameter tool.

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?

States a specific verb+resource ("Archive a project"), which is immediately distinguishable from create_project/get_project/update_project. It does not name restore_project as the counterpart, so sibling differentiation is only partial.

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?

The only guidance is the precondition "Requires confirm=true" — a mechanical requirement, not a when-to-use rule. There is no statement about when archiving is appropriate versus updating or restoring a project.

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