Skip to main content
Glama

save_project_config

Store project configuration in .vscode-mcp.toml to apply workspace-specific settings for tool execution.

Instructions

Save project-specific configuration to .vscode-mcp.toml

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesProject configuration object
pathNoPath to workspace directory (defaults to current)

Implementation Reference

  • The core handler function 'saveProjectConfig' that saves project configuration to .vscode-mcp.toml. It serializes the config using TOML, writes it to disk, updates the cache, and returns a ToolResult.
    async saveProjectConfig(config: ProjectConfig, workspacePath?: string): Promise<ToolResult> {
      try {
        const resolvedPath = workspacePath || this.workspaceService.workspacePath;
        const configPath = path.join(resolvedPath, ProjectConfigService.CONFIG_FILENAME);
        
        const tomlContent = toml.stringify(config as any);
        await fs.writeFile(configPath, tomlContent, 'utf-8');
        
        // Update cache
        this.configCache.set(configPath, config);
        
        return {
          content: [{
            type: 'text',
            text: `Project configuration saved to ${configPath}`
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{
            type: 'text',
            text: `Failed to save project configuration: ${error}`
          }]
        };
      }
    }
  • The tool definition/input schema for 'save_project_config', declaring the required 'config' (object) and optional 'path' (string) input parameters.
    {
      name: 'save_project_config',
      description: 'Save project-specific configuration to .vscode-mcp.toml',
      inputSchema: {
        type: 'object',
        properties: {
          config: { type: 'object', description: 'Project configuration object' },
          path: { type: 'string', description: 'Path to workspace directory (defaults to current)' }
        },
        required: ['config']
      }
    },
  • src/index.ts:258-259 (registration)
    The tool handler registration in the switch statement of executeToolCommand, routing 'save_project_config' to projectConfigService.saveProjectConfig(args.config, args.path).
    case 'save_project_config':
      return await this.projectConfigService.saveProjectConfig(args.config, args.path);
  • Initialization of the ProjectConfigService instance used to handle the save_project_config tool.
    this.projectConfigService = new ProjectConfigService(this.workspaceService);
  • Internal usage of saveProjectConfig as a helper when adding a command to the allowed commands list in SecureCommandService.
    await this.configService.saveProjectConfig(config);
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'save', not whether it overwrites, merges, creates directories, or requires permissions. The behavior is opaque beyond the basic file write.

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?

A single, front-loaded sentence that efficiently communicates the action and target. No wasted words; every part earns its place.

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?

Given the complex nested object parameter and lack of output schema, the description is insufficient. It does not explain the config structure, overwrite behavior, or error handling, leaving significant gaps for an agent.

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 coverage is 100%, so both parameters are already described. The description adds no additional meaning beyond what is in the schema, meeting the baseline of 3.

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?

The description clearly states the action (save) and the resource (project-specific configuration to .vscode-mcp.toml). It distinguishes itself from siblings like load_project_config and update_project_config by focusing on saving.

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?

No guidance is provided on when to use this tool versus alternatives like update_project_config or load_project_config. There are no prerequisites, exclusions, or context for when this tool is appropriate.

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/agentics-ai/code-mcp'

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