MapleStory MCP Server

get_character_equipment

Retrieve equipped items and stats for a MapleStory character to analyze gear configuration and performance metrics.

Instructions

Retrieve equipment information for a MapleStory character including all equipped items and their stats

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": {
      "characterName": "<characterName>"
    },
    "name": "get_character_equipment"
  }
}

Input Schema

Name	Required	Description	Default
`characterName`	Yes	The name of the character to look up
`date`	No	Date for character equipment in YYYY-MM-DD format (optional, defaults to yesterday)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Mar 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not behavioral traits like rate limits, authentication needs, error handling, or data freshness. It mentions retrieving 'equipment information' but doesn't detail format, pagination, or potential side effects.

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 front-loads the core purpose ('retrieve equipment information') and specifies scope ('including all equipped items and their stats'). There is no wasted verbiage, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the purpose but lacks behavioral details and usage context. Without annotations or output schema, more guidance on return values or operational constraints would improve completeness.

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 description coverage is 100%, with clear descriptions for both parameters (characterName and date). The description adds no additional meaning beyond the schema, such as explaining character name constraints or date usage context, so it meets the baseline for high schema coverage.

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 action ('retrieve equipment information') and the resource ('MapleStory character'), specifying the scope as 'all equipped items and their stats'. It distinguishes from siblings like get_character_basic_info or get_character_stats by focusing specifically on equipment, though it doesn't explicitly contrast them.

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 get_character_full_info (which might include equipment) or get_character_stats (which might overlap with stats). The description implies usage for equipment retrieval but lacks explicit context or exclusions.

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

Deploy Server