humanagent-mcp

get_human

Retrieves detailed profiles of human service providers, including skills, reviews, and availability, to help AI agents evaluate and hire the right person for physical-world tasks.

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_human"
  }
}

Input Schema

Name	Required	Description	Default
`human_id`	Yes	人类 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.11Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the type of information returned (skills, reviews, availability), which is helpful. However, it does not mention error handling, authentication, or any caveats about the returned data (e.g., only active humans).

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, front-loaded sentence with no filler words. It efficiently conveys the tool's purpose and key content.

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 one-parameter get tool without an output schema, the description is mostly complete: it states the purpose and enumerates key fields. It could be improved by referencing the required human_id or contrasting with search_humans, but it is adequate.

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?

The schema already describes the sole parameter human_id with 100% coverage, so the description need not add parameter information. It does not, but the schema suffices.

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 ('获取' get) and the resource ('人类服务者的详细信息' detailed information about human service providers), and specifies the content (skills, reviews, availability). This distinguishes it from siblings like search_humans (search) and get_agent_identity (agent, not human).

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 the tool is for retrieving a specific human's details, but it does not explicitly say when to use it over search_humans or mention any prerequisites. The context is clear but no alternatives are mentioned.

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