Skip to main content
Glama
上海大学狐友 MCP

上海大学狐友 MCP

get_huyou_post

Read-only

Retrieve public Shanghai University Huyou post details, comments, and nested replies by post ID or public URL, so AI clients can read community discussions without an account.

Instructions

查看上海大学狐友公开帖子详情、评论和楼中楼,target 为帖子 ID 或公开 URL。

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": {
      "target": "<target>"
    },
    "name": "get_huyou_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
refreshNo
reply_limitNo
comment_limitNo
with_discussionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, non-destructive behavior, so the description need not repeat safety profile. The description adds that only public posts are accessible and that target accepts either a post ID or a public URL, which is useful context. It does not explain the non-idempotent hint or refresh behavior, leaving some behavioral gaps.

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?

The description is a single, front-loaded sentence with no redundant wording. It efficiently conveys the resource scope and the target format.

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?

For a tool with five parameters and zero schema descriptions, the description is too terse to support complete invocation. It covers the required target but omits any meaningful explanation of refresh, reply_limit, comment_limit, or with_discussion, which are essential for controlling the returned content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains only the required target parameter (post ID or public URL). The four optional parameters—refresh, reply_limit, comment_limit, and with_discussion—are not mentioned at all, despite schema description coverage being 0%. This leaves an agent unable to interpret how to use those controls beyond their titles and defaults.

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 states a specific verb (查看) and resource (上海大学狐友公开帖子详情、评论和楼中楼), making the tool's retrieval purpose clear. It does not explicitly distinguish itself from the sibling search_huyou_posts, but the focus on post detail rather than searching is apparent.

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?

Usage is implied by '查看...详情' and the restriction to '公开' posts, giving some context for when to use it. However, there is no explicit guidance on when to choose this over search_huyou_posts or get_shu_huyou_info, nor are any exclusions stated.

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