Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

restore_project

Restore a soft-deleted ChatCut project (undo delete_project or a dashboard delete) for the signed-in owner. The project reappears in the dashboard and list_projects. Discover deleted projects with list_projects includeDeleted=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": {
      "projectId": "<projectId>"
    },
    "name": "restore_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
timelineIdNo
editorBaseUrlNoEditor origin/base URL. Defaults to CHATCUT_EDITOR_URL or http://localhost:5173.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: the operation is scoped to 'the signed-in owner' and the effect is observable because the project 'reappears in the dashboard and list_projects'. It leaves gaps around idempotentHint=false — what happens if the project was never deleted, or is restored twice, is unstated.

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?

Three short sentences, front-loaded with the operation and its inverse, then the observable result, then the discovery prerequisite. No filler, no restatement of the title or name.

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?

For a mutation tool with no output schema, the description supplies the outcome (project returns to dashboard and list_projects), the authorization scope (signed-in owner), and the discovery path. The remaining gap is failure behavior — restoring a non-deleted project or a project the caller doesn't own is not described.

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 67%, below the threshold where the schema alone carries the burden, and the description adds no parameter guidance at all — it never mentions projectId, timelineId, or editorBaseUrl. Notably timelineId has no description in the schema either, so for a restore operation its relevance to the target is undocumented in both places.

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?

States a specific verb and resource ('Restore a soft-deleted ChatCut project') and immediately disambiguates the operation by naming the inverse tool ('undo delete_project or a dashboard delete'). An agent can distinguish it from delete_project, create_project, and duplicate_project without opening any schema.

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

Usage Guidelines5/5

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

Gives the precondition for use (the project must already be soft-deleted) and the discovery route ('Discover deleted projects with list_projects includeDeleted=true'), naming the exact sibling and argument needed before calling. The alternative of restoring via other means isn't discussed, but the routing guidance is explicit enough that an agent knows precisely when this applies.

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

All ChatCut toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources