renthuman

create_task

Create a task for human executors. Cost = reward × max_executors × 1.2 (20% platform fee), charged from your balance into escrow. Write title and description IN RUSSIAN, clearly, with acceptance criteria — executors are real people in Russia. Returns task_id.

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": {
      "title": "<title>",
      "description": "<description>",
      "reward": "<reward>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description
`city`	No	City in Russia (e.g. "Москва"). Omit for online/any-city tasks
`title`	Yes	Short task title in Russian
`reward`	Yes	Reward per executor in USDT, minimum 1
`category`	No	Task category
`deadline`	No	Deadline as ISO 8601 datetime, optional
`description`	Yes	Detailed instructions and acceptance criteria in Russian
`max_executors`	No	How many humans needed, 1-100. Default 1

Output Schema

Name	Required	Description
`cost`	No	USDT charged into escrow (reward × executors × 1.2)
`balance`	No	Remaining balance after the charge
`task_id`	Yes	UUID of the created task

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "balance": {
+      "description": "Remaining balance after the charge",
+      "type": "number"
+    },
+    "cost": {
+      "description": "USDT charged into escrow (reward × executors × 1.2)",
+      "type": "number"
+    },
+    "task_id": {
+      "description": "UUID of the created task",
+      "type": "string"
+    }
+  },
+  "required": [
+    "task_id"
+  ],
+  "type": "object"
+}

First observedJun 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses behavioral traits beyond annotations: cost calculation, escrow charging, Russian language requirement, and return of task_id. No contradiction with annotations; it adds useful context not covered by readOnlyHint=false or openWorldHint=true.

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 two concise sentences with no filler. It front-loads purpose and efficiently covers cost, language, audience, and return value.

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?

Given the tool complexity (7 parameters, cost formula, language constraint) and the existence of an output schema, the description is mostly complete. It could mention potential errors or authorization needs, but overall it adequately covers key aspects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds additional meaning: cost formula (reward * max_executors * 1.2) and emphasis on Russian language, which are not in the schema. This enriches 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 it creates a task for human executors. The verb 'create' and resource 'task' are explicit, and it distinguishes itself from sibling tools like cancel_task or list_tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides specific usage guidance: write in Russian, include acceptance criteria, target audience is Russian executors, and cost formula. It implies when to use this tool but does not explicitly state when not to use it or mention alternatives.

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

All renthuman tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?