Skip to main content
Glama

get_project_info

Retrieve Synthesizer V Studio project details to understand the current vocal track setup for editing lyrics and melodies.

Instructions

Get information about the current Synthesizer V Studio project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_project_info' MCP tool. Executes the command via file-based IPC to the Synthesizer V Studio Lua script and returns the project information as a JSON-formatted text content block.
    case "get_project_info": {
      const projectInfo = await executeCommand("get_project_info");
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(projectInfo, null, 2)
        }]
      };
    }
  • src/index.ts:244-252 (registration)
    Registration of the 'get_project_info' tool in the ListTools handler. Defines the tool name, description, and empty input schema (no parameters required).
    {
      name: "get_project_info",
      description: "Get information about the current Synthesizer V Studio project",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema for the 'get_project_info' tool, specifying an empty object (no input parameters).
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
  • Core helper function used by the tool handler to send the 'get_project_info' command to the external Lua script via temporary JSON files and retrieve the response.
    async function executeCommand(action: string, params: any = {}): Promise<any> {
      const command = {
        action,
        ...params
      };
    
      await writeCommand(command);
      return await readResponse();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states this is a read operation ('Get information'), but doesn't describe what specific information is returned, whether it's cached, requires authentication, has rate limits, or what happens if no project is open. This leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that gets directly to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information about what the tool does.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and sibling tools that might overlap in functionality, the description is insufficiently complete. It doesn't explain what 'information' means in this context, what format it returns, or how it differs from other information-retrieval tools in the server, leaving the agent with significant uncertainty.

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 has zero parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose. A baseline of 4 is appropriate for zero-parameter tools.

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 clearly states the verb ('Get') and resource ('information about the current Synthesizer V Studio project'), making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like 'list_tracks' or 'get_track_notes' that might also retrieve project-related information, preventing a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'list_tracks' and 'get_track_notes' available, there's no indication whether this tool provides broader project metadata, summary information, or should be used as a first step before other operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ocadaruma/mcp-svstudio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server