MapleStory MCP Server

get_character_basic_info

Retrieve basic MapleStory character details including level, job, world, and guild affiliation by providing a character name.

Instructions

Retrieve basic information about a MapleStory character including level, job, world, and guild

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_basic_info"
  }
}

Input Schema

Name	Required	Description	Default
`characterName`	Yes	The name of the character to look up
`date`	No	Date for character info 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?

No annotations are provided, so the description carries full burden. It states this is a retrieval operation but doesn't disclose behavioral traits such as whether it's read-only, requires authentication, has rate limits, or how it handles errors. For a tool with no annotations, this is a significant gap in transparency.

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 purpose and key data fields without any wasted words. It's appropriately sized for a simple lookup tool and earns its place by clearly stating what the tool does.

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 low complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It explains what data is retrieved but lacks context on usage versus siblings and behavioral details. With no output schema, it could benefit from hinting at return values, but the simplicity keeps it from being incomplete.

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 in the input schema. The description adds no additional parameter semantics beyond what's already documented in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 verb ('retrieve') and resource ('basic information about a MapleStory character'), and specifies key data fields (level, job, world, guild). However, it doesn't explicitly differentiate from siblings like get_character_full_info or get_character_stats, which likely provide overlapping or more detailed information.

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 like get_character_full_info or get_character_stats. It mentions what data is retrieved but not the context or trade-offs compared to sibling tools, leaving the agent to guess based on tool names alone.

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

Deploy Server