Skip to main content
Glama
ispace-top

mcp-server-ispace-wiki

Official
by ispace-top

wiki_update_document

Update iSpace Wiki document fields including title, content, status, or tags. Only send the fields you want to modify.

Instructions

更新文档标题、内容、状态或标签。只传要修改的字段。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
tagsNo
doc_idYes
statusNo
contentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided. Description only mentions partial update but does not disclose idempotency, permission requirements, side effects, or return behavior. Insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise: one sentence plus an instruction. No redundancy, but could benefit from more structure given the complexity.

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?

Despite having an output schema, description provides no information about return values, error conditions, or usage context. Incomplete for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. Description loosely maps 'title' to name, but does not explain status values, tags format, or doc_id context. Fails to add meaningful parameter detail.

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?

Description clearly states the action (update) and resource (document) and lists specific fields (title, content, status, tags), distinguishing it from create, delete, and get siblings.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or exclusions mentioned. The partial update hint is implicit but not explicit about when to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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