Skip to main content
Glama
Sign In
noyacg-mcp

noyacg-mcp

by kwkare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

看帖子与评论

noy_read_post
Read-only

Retrieve a post's full text, images, flags, likes/replies, and first-page comments to review discussion context and preview nested replies.

Instructions

读取一个帖子的完整内容（正文、图片、模糊标记、点赞/回复数）和第一页评论（含楼中楼预览）。评论里 reply_id=-1 是顶层评论；要看完整楼中楼用 noy_read_comment_replies。正文里的 [noygirl:yeah] 是表情包代码、NID123 是书籍引用，都是纯文本存储、前端渲染。

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": {
      "post_id": "<post_id>"
    },
    "name": "noy_read_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultNo是否请求成人向内容（allow-adult 请求头）。不传则用环境变量 NOY_ALLOW_ADULT，默认 false。注意 /api/home 的服务端默认值是 true（不带就是 R18），本项目会显式传 false。
post_idYes帖子 ID（社区列表里的 id）
comment_limitNo展示多少条评论（0 = 只看帖子）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the scoping detail: only the first page of comments is returned, reply_id=-1 marks top-level comments, and the [noygirl:yeah]/NID123 tokens are plain text rendered by the frontend. That is genuinely useful non-obvious behavior beyond the structured fields.

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 main capability leads, followed by comment-structure semantics and then rendering notes. It is dense but every sentence carries distinct information; the middle clause about reply_id is slightly compressed but not wasteful.

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, yet the description enumerates the returned fields and clarifies comment paging and inline token formats, which is exactly the information an agent needs to interpret results. Nothing material is missing for a read-only single-post fetch.

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% and the schema already explains adult, post_id, and comment_limit in detail (including the /api/home default caveat). The description only implicitly links '第一页评论' to comment_limit, adding nothing the schema lacks, so the baseline 3 applies.

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?

First sentence states a specific verb and resource (读取一个帖子) and enumerates exactly what is returned: 正文、图片、模糊标记、点赞/回复数、第一页评论. It is clearly distinguishable from noy_list_posts (listing) and noy_read_comment_replies (deeper replies), both of which appear in the sibling list.

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?

Explicitly routes the agent to noy_read_comment_replies when full 楼中楼 is needed, and implies use for a single post's full read. It does not state exclusions beyond that (e.g., when to prefer noy_home_feed), so it stops just short of full when/when-not guidance.

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