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

mcp-server-fanqie

by fysh1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

register_device

Register a new Android or iOS device to the FanQie device pool for accessing novels.

Instructions

Register a new device to the device pool

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "register_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoPlatform type: android or iosandroid

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?

With no annotations, the description carries full burden for behavioral disclosure, but it provides none. It does not mention side effects, authentication requirements, rate limits, or what happens if the device is already registered. The description adds no value beyond the basic action.

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

Conciseness4/5

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

The description is a single sentence with no superfluous words, achieving high conciseness. However, it sacrifices informativeness; with more to convey, a slightly longer description would be justified.

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 the tool's simplicity (single parameter, no output schema), the description is too minimal. It captures the basic purpose but lacks details on return values, error conditions, or behavioral context needed for reliable AI invocation. The agent must infer too much.

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 100% of the parameters with descriptions (e.g., 'platform: Platform type: android or ios'), so the baseline is 3. The description does not add any additional parameter context beyond what the schema already provides, but it does not reduce clarity either.

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 action ('Register') and the resource ('a new device to the device pool'), providing a specific verb+resource. However, it does not distinguish itself from the sibling tool 'register_ios_device' which suggests a more specific use case. The input schema reveals it handles both 'android' and 'ios' platforms, but this is not mentioned in the description.

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 provided on when to use this tool versus alternatives like 'register_ios_device'. The description lacks context about prerequisites, suitability, or exclusions. An AI agent would have no basis to decide between this tool and its siblings.

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