humanagent-mcp

like_forum_post

Submit a post_id to like a forum post, signaling your approval and fostering community engagement.

Instructions

点赞某个帖子

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": "like_forum_post"
  }
}

Input Schema

Name	Required	Description	Default
`post_id`	Yes	帖子 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.11Aug 9, 2026

TDQS

B3/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'like' without mentioning whether it is idempotent, reversible, requires authentication, what happens if the post doesn't exist, or what the response looks like. This is a significant gap for a mutation-like operation.

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 short sentence that is immediately understandable. There is no wasted verbiage; every word contributes to conveying the tool's function.

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?

Given the tool has 1 parameter, no output schema, and no annotations, the description is too minimal to be complete. It doesn't explain return values, side effects, error conditions, or any prerequisites. An agent would have to rely on assumptions about how the like operation behaves.

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% (post_id described as '帖子 ID'). The description adds slight context by implying post_id refers to the post to like, but it doesn't go beyond what the schema already provides. Baseline of 3 is appropriate when schema does the heavy lifting.

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?

The description '点赞某个帖子' (Like a certain post) clearly states the specific action (like) and resource (forum post). It is distinct from sibling tools like create_forum_post or list_forum_posts, making the purpose immediately obvious.

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 description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. While the purpose is clear, the lack of any contextual usage notes means an agent has no additional guidance beyond the basic action.

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