Tomato Writer MCP

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v2.0.0
Disambiguation4/5
Most tools target distinct actions, but get_current_novel overlaps somewhat with list_novels, and get_novel_stats overlaps with list_chapters on chapter-level data. Descriptions are clear enough to resolve most ambiguity.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern: list_*, get_*, switch_*, publish_*. No mixed conventions or vague verbs.
Tool Count5/5
Seven tools is well-scoped for a novel publishing and stats workflow. Each tool covers a necessary step from authentication through novel selection, chapter listing, publishing, and data retrieval.
Completeness4/5
The core workflow is complete: login, choose novel, list chapters, publish, and fetch stats. Minor gaps exist for chapter detail/edit/delete operations and novel creation, but they are not essential to the stated publish-and-monitor purpose.
Average 4.1/5 across 7 of 7 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 2 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. '查看' implies a read-only operation, which is useful, but the description does not state what happens if no novel is selected, whether side effects occur, or what the returned data represents. It is minimally transparent but not richly detailed.
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?
The description is a single, front-loaded sentence with no filler words. Every phrase earns its place by identifying both the action and the target resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter getter, the description is mostly adequate, but with no output schema and no annotations, it does not clarify the return shape or behavior in edge cases such as no current selection. The low complexity and clear siblings partially compensate, leavig some gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is .,% so there is nothing the description needs to explain about parameter syntax. The description adds the meaningful context that the operation targets the currently selected novel, which is sufficient for a parameterless tool.
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 uses a specific verb ('查看') plus a specific resource ('当前选中的小说'), which clearly identifies the tool's function. It also distinguishes itself from siblings like list_novels and switch_novel by focusing on the current selection rather than listing or switching.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase '当前选中的' implies this tool should be used when the agent needs the currently active novel, likely after a switch_novel operation. However, it does not explicitly mention alternatives, exclusion conditions, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It does state the operation is a read ('获取'), the data categories included, and the default selection behavior. It does not disclose error behavior, auth requirements, or the exact output structure, which is some gap for a tool with no output schema.
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?
The description is two concise sentences with no filler. It front-loads the core purpose and details in the first sentence, and the default behavior in the second, with every word earning its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity tool with two optional parameters and no output schema, the description provides a solid overview of what data will be returned and how book_id behaves. It could be more complete by describing the shape of chapter details or behavior when no novel is selected, but the essentials for selecting and invoking the tool are present.
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 coverage is 100%, so the schema already documents both parameters. The description reinforces the book_id default and chapter detail meaning but adds no meaningful semantics beyond what the input schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets novel reading statistics, enumerating the specific returned categories: book-level overview (read_count, word count, serialization status) and per-chapter reading/following details. This distinguishes it from siblings like list_novels and list_chapters, which are about listing rather than statistics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for reading statistics and clarifies the default behavior when book_id is omitted, which helps invocation. However, it does not explicitly state when to prefer this tool over alternatives such as list_chapters or get_current_novel, nor does it provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the disclosure burden. It does reveal the key outputs (Base64 PNG and session Token) and the 'real-time' nature, but it does not disclose possible side effects such as whether previous QR codes/tokens are invalidted, whether the token expires, or whether authentication is required before other tools. This is adequate but incomplete.
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 sentence that front-loads the action and outcome with no redundant words. Every part, including the output types (Base64 PNG and session Token), contributes useful information, making it concise and well structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description sufficiently explains the return values (QR code image in Base64 and a session token). It does not explain the surrounding login flow, such as how the token should be used or whether the QR code must be polled, which would make it fully complete, but it covers the core call correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters and 100% coverage, so there is nothing for the description to add about parameters. With no parameters, the baseline is 4 and the description appropriately focuses on outputs rather than inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (获取/get), a clear resource (登录二维码数据源/QR code source and 会话 Token/session token), and distinguishes itself from the sibling novel-management tools. An agent can immediately know this is the login-entry tool, separate from list_novels or publish_chapter.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for login via '扫码登录', and the sibling list shows no other login tool, so usage context is somewhat clear. However, it never explicitly says when to use it (e.g., before other authenticated calls) or mentions any exclusions/alternatives. The guidance is implied, not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses the two content modes, auto-extraction behavior, and immediate vs scheduled publishing, which is helpful. However, it does not mention side effects such as overwriting, authentication requirements, or what the response contains.
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?
The description is one dense, well-structured sentence that front-loads the purpose and then cleanly lays out the alternatives and scheduling behavior. There is no filler or redundant restating of the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 7-parameter tool with no output schema and no annotations, the description covers the essential call contract: the required content-mode combos, optional book routing, author_speak, and scheduling. Missing return-value and error-case details are notable but do not prevent an agent from invoking the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, which gives a baseline of 3, but the description adds real value beyond the schema by explaining the one-of-two content mode relationship, how file+chapter_no work together, and how title is auto-extracted. It also gives an ISO time example for publish_time.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action (publish or schedule-publish a chapter) and a specific resource (a chapter in the current or specified novel). It clearly distinguishes the tool from read-only siblings like list_chapters and get_novel_stats.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly explains when to use the tool and gives explicit internal alternatives: title+content vs file+chapter_no. It does not explicitly say when to prefer sibling tools, but the read/write boundary between publishing and listing or stats tools is self-evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It transparently conveys that this is a read-only listing operation scoped to the current account, and it lists the output fields. It does not mention ordering, pagination, or auth prerequisites, but for a simple list tool the disclosed behavior is adequate.
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?
The description is a single sentence that wastes no words. It front-loads the listing scope, includes the expected output, and ends with a practical usage tip.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter list tool with no output schema, the description is complete: it states scope, response fields, and the intended use case. Nothing critical is missing for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description needs to add no parameter semantics. The baseline of 4 applies because there is nothing ambiguous about invoking an input-free tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses a specific verb ('列出') with a clear resource ('当前账号下的所有小说') and enumerates the returned fields. It is easily distinguishable from siblings like list_chapters or get_novel_stats, which target different scopes or data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use it: when handling multiple novels and needing to select an operation target. It could be slightly stronger by naming alternatives, but the usage context is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
无 annotations，描述承担了行为披露责任。它补充了“含定时待发/已发布状态”以及“不传 book_id 用当前选中的小说”这两个关键行为特征，超出了工具名本身能推断的信息。
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?
描述仅两句话，没有冗余信息。先点明操作对象和范围，再补充状态信息和参数默认行为，结构紧凑且信息密度高。
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
工具复杂度低，只有一个可选参数且无 output schema。描述已覆盖功能、返回状态信息和默认参数行为，足以让智能体能正确选择并调用。
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
schema 已说明 book_id 为可选字符串，描述进一步补充了省略时的默认行为，即使用当前选中的小说。这比单纯标注“可选”更有指导意义。
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
描述使用明确动词“列出”，资源为“小说各分卷下的章节”，并补充了包含定时待发/已发布状态，清楚区分于 list_novels 等兄弟工具。功能边界一目了然。
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
描述了核心使用方式：不传 book_id 时使用当前选中的小说，给出了参数省略时的明确行为。虽未直接列举替代工具，但结合工具名和上下文，使用场景足够清晰。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for disclosing behavior. It explicitly reveals the key side effect: the novel selection persists and affects subsequent publish and data-query operations until another switch. It does not mention return values or failure behavior, but the important stateful behavior is transparent.
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?
The description is a single compact sentence: the action is front-loaded, the lookup hint is in a parenthetical, and the persistence behavior is stated with no filler. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description covers the purpose, the prerequisite workflow, and the persistent side effect. An agent has enough information to decide when to invoke it and what to pass. Omitted return/error details are not necessary for correct selection and invocation at this complexity level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already describes book_id with 100% coverage, so the baseline is 3. The description adds value by showing how to obtain book_id via list_novels and by linking the parameter to the persistent current-novel state. This is beyond what the schema alone conveys.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb ('切换', switch) and a specific resource ('当前要操作的小说', the current target novel), and then defines the consequential behavior: subsequent publishing and data queries operate on this novel until switched again. This clearly distinguishes it from siblings like list_novels and get_current_novel, which inspect or list rather than change state.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear prerequisite: call list_novels first to obtain the book_id. It also explains when the switch matters by stating that later publishing and data queries default to the newly selected novel, which is useful usage context. It does not explicitly say when not to use the tool, but for a simple state-switching tool the guidance is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![tomato-writer-mcp MCP server](https://glama.ai/mcp/servers/ChaEunwooy/tomato-writer-mcp/badges/card.svg)](https://glama.ai/mcp/servers/ChaEunwooy/tomato-writer-mcp)

Score Badge

Copy to your README.md:

[![tomato-writer-mcp MCP server](https://glama.ai/mcp/servers/ChaEunwooy/tomato-writer-mcp/badges/score.svg)](https://glama.ai/mcp/servers/ChaEunwooy/tomato-writer-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/ChaEunwooy/tomato-writer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server