Skip to main content
Glama

project_reopen

Destructive

Saves the tracked project, verifies circuit preservation, closes it normally, then reopens the same project. Stops if saving or normal close is unconfirmed.

Instructions

Save, verify circuit preservation, close normally, then reopen the same tracked project. Stops if saving or normal close is unconfirmed.

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": {
      "session": "<session>"
    },
    "name": "project_reopen"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the risk profile is structured. The description adds real value beyond that: it explains the save-before-close sequence and the guard that aborts the operation if saving or normal close fails, which is exactly the context an agent needs before invoking a destructive tool. It still doesn't say what state could be lost or what is returned on abort.

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 short sentences with the operation order front-loaded and the abort condition stated after. No filler, no repetition of the title or schema.

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 destructive one-parameter tool with annotations covering the safety profile, the description covers the core sequence and failure mode. It omits the meaning of the required session argument and any hint of post-call state, which leaves the definition adequate but not complete.

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% and the single 'session' parameter is never mentioned in the description, so an agent gets no help on whether it is an ID, a name, or a handle, or whether it must reference an already-open project. The description does no work to compensate for the undocumented parameter.

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 concrete multi-step operation ('Save, verify circuit preservation, close normally, then reopen') on a specific resource ('the same tracked project'). That sequence distinguishes it implicitly from project_save, project_close, and project_open, though it never names those siblings explicitly.

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 abort condition ('Stops if saving or normal close is unconfirmed') implies when the tool is safe to run, but there is no explicit guidance on when to choose this compound operation over calling project_save/project_close/project_open separately, nor any stated prerequisites such as an already-open session.

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