D-Tools MCP Server

archive_project

Archive one or more D-Tools SI projects by their IDs, or restore previously archived projects by setting archive to false.

Instructions

Archive or unarchive one or more D-Tools SI projects by their IDs. Set archive to false to restore previously archived projects.

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": {
      "ids": "<ids>"
    },
    "name": "archive_project"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes
`archive`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states the action is reversible (unarchive) but doesn't mention permissions, side effects on related data, or error conditions. Minimal disclosure for a mutation tool.

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?

Two concise sentences, no redundant words. Front-loaded with verb and resource. Every word 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?

The description covers the core functionality and key parameter usage. For a simple tool with two parameters and no output schema, it is nearly complete, though missing context on potential side effects or prerequisites.

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?

With 0% schema coverage, the description adds meaning: it explains the 'archive' parameter's effect (true=archive, false=restore). The 'ids' parameter is implied by 'by their IDs,' but no further details on format or constraints. Significant value added for the archive parameter.

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 the action (archive/unarchive), the resource (D-Tools SI projects), and the method (by IDs). It distinguishes from sibling tools like update_project by focusing specifically on the archive state.

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 description explains how to archive (with true/default) and unarchive (with false), but lacks explicit guidance on when to use this tool versus alternatives like update_project or other project-related tools.

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