Skip to main content
Glama

project_open

Destructive

Open a .pdsprj project directly and wait until its window settles while recording processes and crash evidence; reuse a session or stop, save, and close the owned session before switching files.

Instructions

Open a .pdsprj directly, return once the project window settles, record processes and crash evidence. With session, reuse the same project or stop/save/close that owned session before switching files. No input emulation.

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": {
      "path": "<path>"
    },
    "name": "project_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
sessionNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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; the description earns credit by explaining what that destruction means in practice (an owned session may need to be stopped/saved/closed before switching files) and by disclosing the timing contract and side effect of recording processes and crash evidence. It stops short of describing failure modes or what happens if the window never settles.

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?

Three tight sentences, front-loaded with the action and completion condition, then the session rule, then a constraint. 'No input emulation' is terse to the point of being cryptic but is not padding.

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, GUI-launching tool with no output schema and 0% schema coverage, the description covers the session-ownership hazard and the settle-then-record contract reasonably well but leaves 'wait_seconds' unexplained and does not say what the recorded process/crash evidence yields to the caller.

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 description coverage is 0%, so the description must carry parameter meaning. It clarifies 'path' (a .pdsprj opened directly) and 'session' (reuse versus owned-session teardown), but 'wait_seconds' is never mentioned despite 'return once the project window settles' hinting at a bounded wait. Partial compensation only.

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 states a concrete verb and resource: 'Open a .pdsprj directly', and adds the completion condition ('return once the project window settles'). It does not explicitly contrast itself with siblings such as project_reopen or project_create, so the agent must infer the distinction from the names alone.

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?

It gives conditional guidance for the session path: reuse the same project, or stop/save/close the owned session before switching files. 'No input emulation' sets a usage boundary. However, there is no clear statement of when to pick this over project_reopen/project_create, so usage is implied rather than spelled out.

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