Skip to main content
Glama
Sign In
RPG Maker MZ Authoring MCP

RPG Maker MZ Authoring MCP

by NixonMSilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

database set class curve

database_set_class_curve

Regenerate a class parameter curve from level-1 and level-99 values using linear, ease-in, or ease-out shapes, or set all 100 values explicitly with preview-first validation.

Instructions

Regenerate one class parameter curve from level-1 and level-99 values (shape linear | ease_in | ease_out), or set all 100 values explicitly.

Preview-first: returns a change set (normalized + native diff, validation incl. reverse references). Pass apply=true to commit immediately when the preview is clean.

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": {
      "classId": "<classId>",
      "param": "<param>"
    },
    "name": "database_set_class_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNoCommit right after a successful preview (non-destructive operations only; needs --allow-write; warnings also need acknowledgeWarnings). Default false = preview only.
paramYesParameter: 0-7 or "mhp", "atk", "Max HP", ...
shapeNo
level1No
valuesNo
classIdYes
level99No
allowScriptNotrue ONLY if the user explicitly asked to insert JavaScript (script commands, script conditions/operands, route scripts).
descriptionNoOptional description stored in the transaction log
acknowledgeWarningsNoAccept validation warnings when apply=true. Review them with the user first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and non-idempotent, so the safety profile is largely covered; the description still adds real value by disclosing that the default call returns a change set with normalized and native diffs plus validation including reverse references. It omits what happens to the existing 100 values when the curve is regenerated, and there is mild tension in calling a full overwrite 'non-destructive'.

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 tight paragraphs, front-loaded with the operation and the two input modes, then the preview/commit rule. No sentence is 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?

No output schema exists, and the description usefully explains what the preview returns (change set, normalized and native diff, validation with reverse references). For a 10-parameter mutation tool it is nearly complete, missing only the effect on existing values and any note on the exact length requirement for the values array.

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?

With only 50% schema coverage across 10 parameters, the description compensates by explaining the semantics of the core pairings: shape with level1/level99 interpolates, while values supplies all 100 points explicitly, and apply governs preview vs commit. It adds no meaning for classId, param, allowScript, description or acknowledgeWarnings beyond what the schema already says.

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 precise verb and resource: 'Regenerate one class parameter curve' and names the two input modes (level1/level99 with a shape, or all 100 values explicitly). That is far more specific than the generic CRUD siblings, though it never names which sibling to use instead.

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 clear operational guidance: preview-first by default, and pass apply=true to commit 'when the preview is clean', which is exactly the when-to-use condition an agent needs. It does not state when to prefer this over database_update_record or when the shape mode is unsafe relative to explicit values.

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

Deploy Server

Other Tools