Retrieves a character's V Matrix details, including 5th job skill cores, from MapleStory using the character OCID and an optional date.
캐릭터 V매트릭스(5차 스킬 코어) 정보를 조회합니다.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | 조회 기준일 (YYYY-MM-DD) | |
| ocid | Yes | 캐릭터 OCID |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. The word '조회합니다' clearly indicates a read-only lookup, which is useful, but the description does not disclose any further behavioral traits such as date applicability, limitations, or prerequisites.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded Korean sentence with no filler or redundant wording. Every phrase contributes meaningful information about the resource being queried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema and output schema cover parameter and return expectations, and the purpose is clear. However, the description lacks usage guidance and richer behavioral context, which matters given the large set of sibling character-information tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents both parameters with 100% coverage. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('조회합니다'), a clear resource ('V매트릭스'), and a clarifying qualifier ('5차 스킬 코어'). This makes the tool's function unambiguous and helps distinguish it from related sibling tools like get_character_hexamatrix.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool should be used when V Matrix information is needed, but it does not explicitly explain when to use this tool instead of alternatives or when not to use it. The agent must infer usage from the tool name and sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.