Skip to main content
Glama
Sign In
noyacg-mcp

noyacg-mcp

by kwkare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

社区帖子列表

noy_list_posts
Read-only

Browse community post lists sorted by newest or most liked, with page-by-page summaries and a pinned post on page one. Use it to discover posts before reading full comments or content.

Instructions

按最新或最热翻社区帖子列表（每页约 40 条）。第 1 页会多带一条置顶帖；len 是近似总数会浮动，判断是否到底请用 over。列表里没有评论内容，要看评论用 noy_read_post。

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

Input Schema

NameRequiredDescriptionDefault
pageNo页码，从 1 开始
sortNonew = 最新；like = 热门new
adultNo是否请求成人向内容（allow-adult 请求头）。不传则用环境变量 NOY_ALLOW_ADULT，默认 false。注意 /api/home 的服务端默认值是 true（不带就是 R18），本项目会显式传 false。
limitNo返回多少条摘要

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint), but the description adds real behavioral context: ~40 items per page, page 1 carries an extra pinned post, and `len` is an approximate, drifting count that should not be used for end-of-list detection. These are non-obvious traits an agent would otherwise get wrong.

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 tight sentences with no filler; the page-size and pinned-post caveats come first, and the routing hint to noy_read_post comes last. Every clause carries information.

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?

With no output schema, the description correctly explains the semantics of `len` and `over` in the response, which is exactly the gap it needed to fill. Minor omission: no mention of filtering or what a post summary contains.

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 coverage is 100%, so page/sort/adult/limit are all documented in the schema itself. The description adds only the approximate page-size and pinned-post behavior, which is helpful but marginal relative to the schema's own detail.

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 and resource (paging through community post lists) plus the sort modes it supports, and explicitly contrasts with noy_read_post for comment content. It does not distinguish itself from the sibling noy_home_feed, so it falls short of a 5.

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 clear when-to-use-else guidance for the most likely confusion: '列表里没有评论内容，要看评论用 noy_read_post'. Pagination guidance ('判断是否到底请用 `over`') is also actionable. Missing: when to pick this over noy_home_feed.

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