Skip to main content
Glama
devmagary
by devmagary

create_weapon

Create a weapon in the RPG Maker MZ database with specified name, description, price, attack power, and optional element type to define its combat properties.

Instructions

Create a new weapon in the database with attack power and optional element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWeapon name
descriptionYesWeapon description
priceYesWeapon price
wtypeIdNoWeapon type ID (1=Dagger, 2=Sword, 3=Flail, etc.)
attackNoAttack power (ATK bonus)
elementIdNoElement ID (1=Physical, 2=Fire, 3=Ice, 4=Thunder, etc.)
iconIndexNoIcon index from IconSet
animationIdNoAttack animation ID
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states the operation is a creation, but does not mention return value, error cases, side effects, or any constraints. The agent has no information on whether creation is idempotent, what happens on duplicate name, etc.

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, clear sentence with no superfluous words. It immediately states the tool's purpose and key attributes.

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?

The description lacks context for a tool with 8 parameters and no output schema. It does not mention that it returns the created weapon, what the defaults are, or any behavior upon success/failure. The tool's complexity demands more explanatory context.

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 baseline is 3. The description mentions two parameters ('attack power' and 'optional element') but does not add any additional semantics beyond what is already in the schema descriptions. No clarification of defaults, relationships, or constraints.

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 (create) and resource (weapon) with specific attributes (attack power, optional element). It distinguishes from sibling create tools for other entities and from update_weapon.

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 usage guidelines provided. The description does not indicate when to use this tool over alternative create tools or update_weapon. No context about prerequisites or limitations.

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/devmagary/MCP-Maker'

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