get_current_novel
Retrieve details of the currently selected novel for author management tasks.
Instructions
查看当前选中的小说。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve details of the currently selected novel for author management tasks.
查看当前选中的小说。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description implies a read operation ('view'), but doesn't disclose if it requires authentication, returns metadata vs content, or if it fails without a selected novel.
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?
Single sentence, front-loaded with the action and object. No extraneous words.
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?
Given simplicity (no params, no output schema), the description is nearly complete. However, adding context about what 'current novel' means or how selection works would improve it.
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?
No parameters exist; the schema is empty. Baseline of 4 applies as per instructions, and the description adds no parameter info beyond what the schema provides.
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 clearly states the verb '查看' (view) and resource '当前选中的小说' (currently selected novel), distinguishing it from siblings like 'list_novels' and 'switch_novel'.
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, such as setting a novel selection first with 'switch_novel'. The description lacks prerequisites or exclusion criteria.
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/fuhei/tomato-writer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server