humanagent-mcp

get_reviews

Retrieve the review and rating history of a human service provider to evaluate their past performance and reliability.

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": {
      "human_id": "<human_id>"
    },
    "name": "get_reviews"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	返回评价数量
`human_id`	Yes	人类 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.11Aug 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It states the primary function but omits details such as whether the operation is read-only (though implied by 'get'), error handling, rate limits, or how results are ordered. The minimal description leaves the agent uncertain about expected behavior.

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, concise sentence in Chinese that directly conveys the core purpose. It is front-loaded with the verb and resource, with no unnecessary words or repetition.

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?

The description lacks important context given no output schema is present. It does not explain return format, pagination behavior, or how the limit parameter affects results. While the schema covers parameters, the description fails to provide a complete picture for an agent to invoke the tool correctly.

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 description coverage is 100%, with both limit and human_id having descriptions. The tool description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance parameter understanding.

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's function: retrieving the review and rating history of human service providers. It uses a specific verb ('获取' / get) with a clear resource, distinguishing it from sibling tools like get_human or list_skills.

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?

No guidance is provided on when to use this tool over alternatives or any exclusions. The description simply defines what it does without offering context on prerequisites, such as needing a valid human_id or when to use get_human instead.

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