Skip to main content
Glama
garuh143

RPG Maker MZ/MV MCP Server

by garuh143

update_skill

Modify skill properties in RPG Maker MZ/MV projects by specifying skill ID and desired changes to attributes, effects, or parameters.

Instructions

Update a skill's properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skillIdYesThe skill ID to update
updatesYesProperties to update

Implementation Reference

  • The implementation of the update_skill tool, which finds a skill by ID and updates its properties.
    export async function updateSkill(
      projectPath: string,
      skillId: number,
      updates: Partial<Skill>
    ): Promise<Skill> {
      const skills = await getSkills(projectPath);
      const skillIndex = skills.findIndex(skill => skill && skill.id === skillId);
    
      if (skillIndex === -1) {
        throw new Error(`Skill with ID ${skillId} not found`);
      }
    
      skills[skillIndex] = { ...skills[skillIndex], ...updates };
    
      const skillsPath = getDataPath(projectPath, 'Skills.json');
      await writeJsonFile(skillsPath, skills);
    
      return skills[skillIndex];
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Update' implies mutation, the description fails to specify whether this performs a partial update (merging properties) or full replacement, what happens if the skillId doesn't exist, or whether the operation is idempotent.

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?

The single-sentence description is appropriately brief and front-loaded with the action verb. While minimal, it does not contain redundant or wasteful language—every word serves the purpose statement, even if underspecified for the tool's complexity.

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 this is a mutation tool with nested object parameters and no output schema or annotations, the description is incomplete. It lacks critical operational context such as valid property names for the 'updates' object, error handling behavior, or return value structure that an agent would need to use the tool effectively.

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?

The input schema has 100% description coverage ('The skill ID to update', 'Properties to update'), establishing a baseline score of 3. The description mentions 'properties' which loosely aligns with the 'updates' parameter, but adds no additional semantic details, examples, or constraints beyond what the schema already provides.

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 uses a clear verb ('Update') and identifies the target resource ('a skill's properties'), establishing the tool's function adequately. However, it lacks explicit differentiation from siblings like 'create_skill' or 'get_skill' that would help an agent understand this modifies existing resources versus creating new ones.

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 (e.g., 'create_skill' for new skills), nor does it mention prerequisites such as the skill needing to exist beforehand. There are no exclusions or conditional usage notes.

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/garuh143/RPG-MakerMV-MCP'

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