humanagent-mcp

accept_bounty_application

Accept a human's application for a task and confirm them as the executor. Use this to finalize assignments for physical-world tasks like meetings or errands.

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>",
      "application_id": "<application_id>"
    },
    "name": "accept_bounty_application"
  }
}

Input Schema

Name	Required	Description	Default
`bounty_id`	Yes	任务 ID
`application_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?

No annotations are present, so the description carries the full burden of behavioral disclosure. It states the core action but does not mention side effects (e.g., whether the application is marked as accepted, whether other applications are rejected, or if the action is reversible). This leaves the agent without critical safety context for a mutation operation.

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 sentence with no unnecessary words. It is front-loaded with the verb and object, making it easy to scan and understand immediately.

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 simple two-parameter tool, the description is minimal but misses important contextual information such as post-acceptance effects, whether the operation is idempotent, and any preconditions. The presence of sibling tools like 'complete_bounty' creates ambiguity about the lifecycle stage this action occurs at, which the description does not resolve.

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?

Both parameters are fully documented in the schema (100% coverage), so the description need not repeat them. It does add minor context that the application belongs to a human applicant, clarifying the role of 'application_id', but this is marginal beyond the schema's '申请 ID' label.

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 uses a specific verb '接受' (accept) and clearly identifies the resource (a human's application) and the outcome (confirm that human executes the task). This distinguishes it from sibling tools like 'get_bounty_applications' which only lists applications, and 'complete_bounty' which marks completion.

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 given on when to use this tool versus alternatives. It does not mention prerequisites (e.g., application must be pending) or contrast with related tools like 'get_bounty_applications' or 'complete_bounty', leaving the agent without clear selection criteria.

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