Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Restore project

restore_project

Restore an archived project to active status by supplying its project ID and setting confirm=true.

Instructions

Restore an archived 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": "restore_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

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description adds that this is a restore of an archived resource and that confirm=true is mandatory, which is meaningful safety context the annotations do not convey. Notably the schema does not list confirm as required, so the description carries information the structured data omits. It still says nothing about reversibility or failure behavior if the project is not archived.

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 very short sentences with zero filler; the operation is front-loaded and the prerequisite follows immediately.

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

Completeness3/5

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

For a three-parameter mutation with no output schema, the definition covers the action and the confirmation gate but omits outcome information an agent would want: what state the project ends up in, whether the call is idempotent, and what happens if the project is not archived. Minimum viable rather than complete.

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%, so the schema documents only the organization parameter. The description compensates for part of the gap by explaining that confirm must be true, but leaves project_id semantics and the interaction between project_id and organization unstated. Adequate but partial.

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 and resource ('Restore an archived project'), which is unambiguous and implicitly the inverse of the sibling archive_project. It does not explicitly name or differentiate against any sibling, 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 Guidelines3/5

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

Usage is implied by the precondition 'archived project', and a hard prerequisite (confirm=true) is given, which is genuinely actionable. There is no explicit when-to-use vs. when-not guidance (e.g., what to do if the project is not archived, or how it relates to update_project).

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