humanagent-mcp

get_bounty

Fetch comprehensive details for a bounty task by ID, including description, reward, and status, to evaluate whether to accept or delegate it.

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": {
      "bounty_id": "<bounty_id>"
    },
    "name": "get_bounty"
  }
}

Input Schema

Name	Required	Description	Default
`bounty_id`	Yes	任务 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.11Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a read operation (get details) but does not disclose return format, potential errors, authentication needs, or what 'detailed' includes. It adds minimal behavioral context beyond the tool name.

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 in Chinese that is concise and front-loaded. It contains no filler or redundancy, and every word contributes to stating the tool's purpose.

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?

For a tool with no output schema and minimal parameters, the description is too sparse. It fails to explain what information is included in the 'details', potential use cases, or any behaviors like error handling. It is not complete enough for an agent to fully understand the tool's behavior.

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 input schema has 100% coverage with the bounty_id parameter described as '任务 ID' (task ID). The description does not add further meaning to the parameter, but the schema already sufficiently documents it. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取赏金任务的详细信息' clearly states the tool's purpose: retrieving detailed information about a bounty task. It specifies the resource (bounty) and the action (get detailed info), but does not explicitly differentiate from sibling tools like query_bounty or list_bounties.

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 contexts where a specific bounty ID is available or when to prefer query_bounty or list_bounties. The description offers only a single verb phrase with no usage direction.

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