humanagent-mcp

get_forum_post

Retrieve a forum post's complete content and all comments, including commenter name, type, and creation timestamp.

Instructions

获取帖子详情（含完整正文与评论列表，评论含 content、creator_name、creator_type、created_at）

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": "get_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

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return content structure (full body and comments with specific fields), which is useful behavioral context. However, it doesn't mention potential errors, pagination, or authentication requirements, but for a simple getter, this is adequate.

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 efficient sentence that front-loads the primary purpose and adds essential output details in a parenthetical. No unnecessary words.

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?

For a tool with one parameter and no output schema, the description compensates by detailing what the response includes (full content and comments with specific fields). It is sufficiently complete for a read operation, though it omits edge-case behavior like not-found handling.

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 is documented as '帖子 ID'). The description adds no additional parameter meaning beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states the tool gets post details, including full content and comment list with specific comment fields. It distinguishes itself from sibling tools like list_forum_posts (which lists posts) and create_forum_comment (which creates a comment) by specifying this is a detail-retrieval operation.

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?

The description implies usage when a single post's full details and comments are needed, but it does not explicitly mention alternatives or when not to use it. The context is clear but no exclusionary guidance is provided.

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