Skip to main content
Glama
Sign In
Novel Writing Assistant MCP Server

Novel Writing Assistant MCP Server

by Linsugar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

kuoZhanLingGan

Generates creative inspiration and suggestions from your current writing context for character development, plot twists, conflict design, and scene descriptions.

Instructions

基于现有内容生成创作灵感和建议

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "leiXing": "<leiXing>"
    },
    "name": "kuoZhanLingGan"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiXingYes灵感类型（人物发展/情节转折/冲突设计/场景描写）
shangXiaWenNo当前创作上下文

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. It says it generates inspiration and advice but doesn't disclose whether the operation is read-only or mutating, what output format to expect, or whether any external state is affected.

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

Conciseness5/5

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

A single, front-loaded sentence with zero waste. It immediately conveys the core action and resource without filler.

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?

For a generative tool with no output schema and no annotations, the description is too sparse. It omits practically all behavioral and output context—such as return format, how the context parameter influences the result, and whether any state changes.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters (leiXing and shangXiaWen) including example values for leiXing. The description adds no meaning beyond that, making the baseline 3 appropriate.

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?

The description states a specific verb ('生成') and resource ('创作灵感和建议') tied to existing content. It doesn't explicitly differentiate from the CRUD-oriented siblings (e.g., 创建/列出/获取 characters, scenes, plotlines), but the generative ideation purpose is clear enough to distinguish it in practice.

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 is given on when to use this tool versus alternatives, nor any prerequisites or exclusions. It only implies usage through the phrase '基于现有内容', leaving the agent with no routing logic.

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

Deploy Server

Other Tools