humanagent-mcp

search_humans

Find hireable humans for physical tasks like meetings and errands. Filter by skill, rate, and location to get work done.

Instructions

搜索可雇佣的人类服务者，可按技能、价格、位置筛选

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_humans"
  }
}

Input Schema

Name	Required	Description
`name`	No	按名字搜索
`limit`	No	返回数量限制
`skill`	No	技能筛选，如 'In-Person Meetings'
`offset`	No	分页偏移
`location`	No	位置筛选
`max_rate`	No	最高时薪限制（人民币）

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 carries full behavioral disclosure burden. It only states the search action and filter capabilities but does not disclose return format, pagination behavior, default ordering, or whether results are limited to active/hireable humans. This is minimal for a search tool.

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?

A single, well-structured sentence that front-loads the action and resource, lists the main filters, and contains no redundant information. It is appropriately sized for the tool's simplicity.

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?

Despite having good parameter schema, the description lacks context on return values, pagination (offset/limit), and behavior when no filters are applied. Since no output schema exists, the description should at least hint at what results look like, but it does not, making it incomplete for an agent to invoke 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 coverage is 100%, so all parameters are documented in the schema. The description's mention of skill, price, and location filters overlaps with schema descriptions but adds no new semantics or syntax details. 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 action ('搜索') and resource ('可雇佣的人类服务者'), and specifies the key filter dimensions (技能, 价格, 位置). This distinguishes it from sibling tool get_human, which presumably retrieves a single human, by focusing on search/filter functionality.

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 versus alternatives. It does not mention get_human for retrieving specific profiles, nor does it note any exclusions, prerequisites, or typical search scenarios.

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