Skip to main content
Glama

Follow a Person

follow_user

关注 PowPow 上的某个人。需要 user_id——先用 search_users 或 get_user_profile 查到对方的 user_id,不要把昵称当 id 传。重复关注不会报错。注意:PowPow 没有「加好友」这个动作,好友 = 互相关注,返回值里的 is_friend 会说明对方是否也关注你。

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": {
      "user_id": "<user_id>"
    },
    "name": "follow_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes要关注的用户 id(36 位,来自 search_users / get_user_profile 的结果)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare this is a non-read-only but non-destructive, closed-world mutation, so the safety profile is covered. The description adds behavior beyond that: duplicate follows are silently idempotent (no error), and the response carries is_friend indicating whether the follow is reciprocated. That is exactly the kind of post-call semantics an agent cannot infer from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each doing distinct work: purpose, prerequisite + id pitfall, idempotency, then the friend-semantics caveat. The id requirement is front-loaded where an agent will read it before constructing arguments.

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?

For a single-parameter mutation with no output schema, the description covers what an agent needs: how to obtain the id, what happens on repeat calls, and what the returned is_friend field means. Nothing material is missing.

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% and the schema already documents the 36-character format and its source, so the baseline is 3. The description adds the practical pitfall that a nickname must not be substituted, which is a semantic constraint absent from the schema; it does not go further into id format edge cases.

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?

"关注 PowPow 上的某个人" states a specific verb (follow) and resource (a PowPow user), and the closing note explicitly disambiguates it from a “friend request” action that does not exist in this product. An agent can distinguish it from unfollow_user, list_friends, or add_favorite without opening any schema.

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

Usage Guidelines5/5

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

It names the prerequisite alternatives by name (search_users / get_user_profile) and the exact condition that selects them (you need the user_id), plus an explicit anti-pattern: do not pass a nickname as the id. The friend = mutual-follow explanation further tells the agent not to look for a separate friend-request tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.