netease_open_entityOpen songs, playlists, albums, or artists directly in the official NetEase Cloud Music client on macOS. Provide a type and ID to navigate to the corresponding page.
通过 macOS 适配器在官方客户端中打开歌曲、歌单、专辑或歌手页面。
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| type | Yes |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate the tool is not read-only, opens the external world, and is non-destructive. The description adds a useful technical detail about the macOS adapter, which implies platform-specific behavior not covered by annotations, but does not disclose side effects like client focus changes or failure behavior if the client is not running. This is adequate given annotation coverage.
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, concise sentence that front-loads the primary action and resource types, with zero waste. It efficiently conveys the core functionality without redundancy.
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?
For a simple open action with only two parameters and no output schema, the description is adequate. It specifies what is opened and the mechanism (macOS adapter). While it could mention prerequisites like client installation, the simplicity of the tool means the description is sufficiently complete for an agent to call it correctly.
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?
Schema coverage is 0%, but the description explicitly lists the allowed types (song, playlist, album, artist), which partially maps to the type parameter enum. It does not explain the id parameter beyond being an identifier, but for a simple two-parameter tool, the description provides enough context to infer usage without fully compensating for the schema gap.
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?
Description clearly states the action (open) and the specific entity types (song, playlist, album, artist) via the official client, which distinguishes it from sibling tools like netease_open_area (which opens a different area) and netease_launch (which launches the app). The verb and resource are explicit and unambiguous.
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?
No guidance is provided on when to use this tool versus alternatives such as netease_song_detail or netease_search. There is no mention of prerequisites or exclusions, leaving the agent to infer that this is for opening pages without any comparative context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.