Skip to main content
Glama

open_project

Destructive

Opens a .dino project file in Dinoctor to replace the current project and return its summary; blocks replacement when unsaved changes exist unless discard is confirmed.

Instructions

Open a project file (.dino) in Dinoctor, the same as File > Open, in place of the open project. Refuses if the open project has unsaved changes, unless discard: true (ask the person first, or save_project before). Returns the opened project's summary. For a new empty project use new_project; for a template use templates.

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": "open_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe project file's full path (see list_projects).
discardNotrue: drop unsaved changes in the open project. Only after the person agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / discard / description
      Added value: +"true: drop unsaved changes in the open project. Only after the person agreed."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds real context beyond them: the precondition that it refuses on unsaved changes, the exact override (discard: true), the requirement to ask the person first, and the return value (the opened project's summary). This tells the agent both the guardrail and the recovery path before it calls.

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 tight sentences, front-loaded with what the tool does and its replacement semantics, followed by the failure/override rule and then sibling routing. No sentence is redundant, and the parenthetical alternatives carry useful information rather than filler.

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

Completeness5/5

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

For a two-parameter mutation tool with no output schema, the definition covers purpose, preconditions, override behavior, and the return value, which is everything an agent needs to invoke it safely. The only omitted detail is error behavior for invalid paths, which is minor given the schema's pointer to list_projects.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds procedural meaning the schema cannot: discard should only be set after the person agrees, or after save_project. The path parameter is only cross-referenced to list_projects via the schema itself, which keeps this just short of a 5.

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 ('Open a project file (.dino)') plus the user-facing analogue (File > Open) and the key side effect ('in place of the open project'). It explicitly distinguishes itself from the closest siblings, new_project and templates, so an agent can route correctly without opening the 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 explicit when-to-use and when-not-to-use guidance: use new_project for an empty project, templates for a template, and save_project (or human confirmation) before opening when there are unsaved changes. The refusal condition and its escape hatch are spelled out rather than implied.

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