Skip to main content
Glama
Sign In
noyacg-mcp

noyacg-mcp

by kwkare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

首页榜单 / 番剧推荐

noy_home_feed
Read-only

Retrieves homepage data: announcements, four book rankings (daily favorites/reads, featured, editor picks), and anime recommendations; supports shelf selection and result limits.

Instructions

读取首页聚合数据：公告、四个书籍榜单（日收藏 / 日阅读 / 推荐位 / 编辑推荐）和番剧推荐（stream）。注意：allow-adult=false 与 true 是两套互斥内容池，标签也会变；stream 只有带 v=3 才返回，本项目已默认带上。

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

Input Schema

NameRequiredDescriptionDefault
adultNo是否请求成人向内容（allow-adult 请求头）。不传则用环境变量 NOY_ALLOW_ADULT，默认 false。注意 /api/home 的服务端默认值是 true（不带就是 R18），本项目会显式传 false。
limitNo每个榜单返回多少条
shelfNo取哪个榜单；all = 全部（每榜按 limit 截断）all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious behavior: the content pool switches wholesale with allow-adult, and the stream ranking is silently gated behind a v=3 request flag — an agent would otherwise be confused by a missing stream. Auth/permission and rate-limit behavior remain unstated.

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?

Two sentences: the first front-loads the payload contents, the second carries only the two caveats that would otherwise cause wrong calls. No restatement of the name or title, no filler.

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?

There is no output schema, and the description compensates by enumerating the returned sections (announcements, four rankings with limits, stream). Combined with the readOnly annotation and fully documented schema, an agent has enough to call it correctly and interpret the result.

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%, so baseline is 3; the description still adds value by explaining that adult selects between two exclusive pools whose tags differ, and that shelf=stream depends on the v=3 flag. It does not detail limit truncation semantics beyond the schema's own wording.

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?

Uses a specific verb (读取) with a specific resource (首页聚合数据) and enumerates exactly what the payload contains: 公告, four named book rankings (日收藏/日阅读/推荐位/编辑推荐) and 番剧推荐 stream. No sibling tool overlaps this scope, so an agent can identify it unambiguously.

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?

Gives actionable context: adult true/false selects two mutually exclusive content pools with different tags, and stream only comes back when v=3 is sent (which the project already does). It stops short of saying when to call this instead of a sibling or when not to call it, but the shelf parameter usage is implied clearly.

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