Skip to main content
Glama
qimao-autopub-mcp
by yangmi829

列出七猫作品

list_books_qimao

Read an author backend's real book list to get true book IDs for long or short works; use cursor pagination and optionally sync long-form titles to a local registry.

Instructions

读取作者后台真实作品列表(拿真实 book_id):kind=long 读长篇(默认),kind=short 读短篇。分页是游标式——把返回里的 next_id 再传回来取下一页。可把结果同步进本地小说登记(sync_local=true,仅 kind=long)。只读 HTTP、不需要浏览器。

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": "list_books_qimao"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNolong=长篇(默认),short=短篇
next_idNo分页游标:传上一次返回的 next_id 取下一页;不传=第一页
sync_localNo是否把后台作品同步为本地小说登记(默认 false,仅 kind=long)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses read-only HTTP access with no browser requirement, explains cursor-based pagination via next_id, and flags the sync_local side effect that writes into the local novel registry. It stops short of noting auth/permission prerequisites for the backend read.

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?

Dense and front-loaded: purpose first, then kind behavior, pagination mechanics, the sync side effect, and the transport note. Every clause adds information, though the kind default and sync_local constraint duplicate 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 list tool with no output schema, the description covers the essential return contract by naming next_id as the cursor and book_id as the payload. Return field details are thin but adequate for correct invocation.

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 all three parameters are already documented in the schema, including the kind enum, cursor semantics, and the kind=long restriction on sync_local. The description largely restates this, so the baseline 3 is 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?

States a specific verb+resource: reading the author backend's real works list to obtain real book_id, with the kind split for long/short. It is clear what it does, though it never explicitly distinguishes itself from the sibling list_short_stories_qimao, which an agent might reasonably confuse with the kind=short path.

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?

Implies the use case (fetch real book_id) and states that sync_local applies only to kind=long, but gives no explicit when-not guidance or routing against siblings like list_book_options_qimao or list_short_stories_qimao. Usage is inferable but not spelled out.

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