Skip to main content
Glama
Sign In
mcp-server-fanqie

mcp-server-fanqie

by fysh1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_chapter_content

Retrieve the full text of a specific novel chapter by providing its chapter ID. Directly returns the chapter content without additional details.

Instructions

Get content of a specific chapter. This is a simplified interface that directly returns chapter text

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": {
      "item_id": "<item_id>"
    },
    "name": "get_chapter_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesChapter ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'simplified' and 'directly returns chapter text', but lacks details on side effects, authentication requirements, rate limits, or what 'directly' implies (e.g., no preprocessing). The transparency is minimal for a read tool.

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 that are front-loaded with the main purpose. Every word earns its place, and there is no redundancy or fluff.

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?

Given no annotations, no output schema, and a sibling list that includes similar tools like get_content and get_raw_content, the description is incomplete. It does not explain return format, error handling, or how it differs from alternatives, leaving gaps for the AI to infer.

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% with one parameter, item_id, described as 'Chapter ID'. The description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

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 clearly states the verb 'Get' and the resource 'content of a specific chapter', and adds 'simplified interface that directly returns chapter text'. However, it does not differentiate from sibling tools like get_content, which may also return chapter content, leading to potential confusion.

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 such as get_content or get_raw_content. The description implies basic usage but does not specify context, prerequisites, or exclusions, leaving the AI without decision support.

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