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

mcp-server-fanqie

by fysh1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_ios_content

Retrieve chapter content from FanQie Novel using the iOS platform interface (8402 algorithm). Requires a chapter ID as input.

Instructions

Get chapter content using the iOS platform interface (signed with the 8402 algorithm). Note: depends on the iOS device pool and may be temporarily unavailable

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_ios_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesChapter ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

The description mentions dependency on the iOS device pool and potential unavailability, plus the signing algorithm. With no annotations, it provides some behavioral context but lacks details on read-only nature, side effects, or error handling.

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, front-loading the core purpose and adding a critical caveat. No unnecessary words or redundancy.

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?

Given the simple schema (one parameter, no output schema) and no annotations, the description provides moderate completeness. It covers the platform dependency and algorithm but omits details about return format, error cases, or expected behavior.

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?

The input schema covers the single parameter item_id with a description of 'Chapter ID'. The tool description adds no additional semantic information beyond what the schema already provides, so it meets baseline with no extra value.

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 tool gets chapter content using the iOS platform interface with a specific algorithm. However, it does not differentiate from sibling tools like get_chapter_content or get_raw_content, which share similar purposes.

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 iOS-signed content but does not explicitly state when to use it versus alternatives. The note about device pool unavailability provides some context, but no exclusions or direct comparisons are given.

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