MapleStory MCP Server

get_notice_list

Retrieve MapleStory game notices and announcements by type, with pagination support for managing large result sets.

Instructions

Retrieve list of MapleStory game notices and announcements

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notice_list"
  }
}

Input Schema

Name	Required	Description	Default
`noticeType`	No	Type of notices to retrieve (optional)	general
`page`	No	Page number for pagination (1-based, optional, defaults to 1)
`limit`	No	Number of notices per page (optional, defaults to 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Mar 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it retrieves a list but doesn't mention whether this is a read-only operation, if authentication is required, rate limits, error conditions, or what the return format looks like. This leaves significant behavioral gaps.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with essential information.

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 the lack of annotations and output schema, the description is insufficiently complete. It doesn't address behavioral aspects like safety, authentication, or return format, leaving the agent with incomplete context for a tool that retrieves potentially complex data.

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 description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions, defaults, and constraints. The baseline score of 3 reflects adequate schema documentation without additional value from the description.

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 list') and resource ('MapleStory game notices and announcements'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'get_notice_detail', which retrieves individual notice details rather than a list.

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_notice_detail' or other sibling tools. It lacks context about appropriate use cases, prerequisites, 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