create-notebook
Create a new notebook in Yinxiang. Specify a name and optionally a stack to organize your notes.
Instructions
建本
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| stack | No |
Create a new notebook in Yinxiang. Specify a name and optionally a stack to organize your notes.
建本
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| stack | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description gives no information about side effects, permissions, or behavior (e.g., whether it overwrites an existing notebook).
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?
While short, the description is under-specified and fails to convey essential information, making it not concise but deficient.
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?
With 2 parameters, no output schema, and no annotations, the description is severely incomplete, leaving the agent without critical information to use the tool 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 description coverage is 0%, and the description does not explain the purpose of the 'name' or 'stack' parameters, nor any constraints or formats.
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 '建本' is essentially a tautology of the tool name 'create-notebook', providing no additional meaning or distinction from sibling tools.
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 given on when to use this tool versus alternatives like update-notebook or delete-notebook. The description does not mention prerequisites or context.
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/ArchChuan/yinxiang-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server