wiki_delete_comment
Delete a comment from an iSpace Wiki document by providing its comment ID.
Instructions
删除某条评论。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| comment_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Delete a comment from an iSpace Wiki document by providing its comment ID.
删除某条评论。
| Name | Required | Description | Default |
|---|---|---|---|
| comment_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description must disclose behavioral traits. It only says 'delete a comment' but does not mention if deletion is permanent, requires permissions, cascades to replies, etc.
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?
Extremely concise (one sentence) but at the cost of missing critical information. It is front-loaded but insufficient.
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 tool with one required parameter and no annotation coverage, the description is severely incomplete. It does not mention return type, side effects, or usage context.
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 description coverage is 0%, and the description does not explain the one parameter 'comment_id' (e.g., where to find it, format). No value added beyond the schema.
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?
Clearly states '删除某条评论' (delete a comment), which is a specific verb + resource. The tool name itself distinguishes it from the sibling tool 'wiki_delete_inline_comment'.
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 on when to use this tool versus alternatives like wiki_delete_inline_comment, or what prerequisites or context are needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ispace-top/mcp-server-ispace-wiki'
If you have feedback or need assistance with the MCP directory API, please join our Discord server