Skip to main content
Glama

reload_project

Refresh the open project from disk after editing its .vpr file via path-based tools, so the editor reflects updated melodies, lyrics, and project data.

Instructions

Reload the open project from disk (File > Revert): use after editing its .vpr with path=... tools. / 開いているプロジェクトをディスクから読み直します(path 指定で .vpr を編集した後に)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reload_project"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. The File > Revert framing hints that in-memory state is discarded and the on-disk version wins, but it never states plainly that unsaved changes are lost, nor what happens if no project is open or if the file on disk is invalid.

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, front-loaded with the action and its analogy, then the trigger condition. The bilingual duplication is a deliberate localization pattern rather than filler.

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 zero-parameter tool with no output schema, this covers what it does and when to invoke it. What is missing is the destructive consequence for unsaved in-memory edits and any indication of failure modes, which matter for a reload/revert operation.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Its mention of path=... tools is contextual framing rather than parameter documentation, which is appropriate here.

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: reload the currently open project from disk, with the File > Revert analogy clarifying that it is the already-open project, not a new one. This implicitly separates it from open_project/new_project, though it never names a sibling explicitly.

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

Usage Guidelines4/5

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

Gives explicit timing guidance — call it after editing the .vpr file via path-taking tools — which is the main non-obvious scenario for this tool. It does not state when not to use it (e.g., instead of open_project when no project is loaded), leaving a small gap.

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