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

上海大学狐友 MCP

search_huyou_posts

Read-only

Search public posts in the Shanghai University Huyou community by keyword, and optionally query local cache or include discussion replies.

Instructions

仅搜索上海大学狐友圈子公开帖子。keywords 为 1-6 个字面关键词;local=true 仅查本地缓存。

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": {
      "query": "<query>"
    },
    "name": "search_huyou_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
localNo
pagesNo
queryYes
offsetNo
keywordsNo
with_discussionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds genuine value by disclosing two behavioral facts not in the annotations: results are restricted to public posts, and local=true switches to cache-only querying. It says nothing about rate limits, result freshness, or what happens when the cache is cold, which would matter given openWorldHint=true.

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?

Two short sentences with no filler; the scope constraint is front-loaded before the parameter notes. The phrasing is terse and slightly telegraphic, but no sentence is wasted.

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 7-parameter tool with a required 'query' parameter and zero schema coverage, the description is far too thin — five parameters including the required one go undocumented. The output schema is present so return values need not be described, but pagination and the query/keywords distinction are missing and would cause real mis-invocation risk.

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?

Schema description coverage is 0% across 7 parameters, so the description carries the full burden, yet it explains only two: keywords (1–6 literal keywords) and local (cache-only). The required 'query' parameter is never mentioned and its relationship to 'keywords' is left ambiguous, and limit/pages/offset/with_discussion are entirely undefined in both schema and description.

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 names a specific verb (搜索/search) and a narrowly scoped resource (上海大学狐友圈子公开帖子), so an agent immediately knows it is a post-search tool rather than a single-post fetch like get_huyou_post. It stops short of explicitly contrasting itself with the sibling tools, but the scope statement ('仅…公开帖子') is concrete enough to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is a boundary condition — only public posts in the SHU Huyou circle are searched — with no statement of when to choose this tool over get_huyou_post or get_shu_huyou_info, and no prerequisites or exclusions beyond that scope note. An agent must infer routing from the tool name alone.

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