renthuman

get_task

Read-onlyIdempotent

Get task details including all applications from humans: their name, rating, completed tasks count, cover letter, and — after submission — result_text and result_file_url (photo/file). Use this to poll for new applications and submitted results.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	Task UUID

Output Schema

Name	Required	Description
`id`	Yes
`title`	No
`reward`	No
`status`	No
`applications`	Yes	Applications from human executors

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "applications": {
+      "description": "Applications from human executors",
+      "items": {
+        "properties": {
+          "cover_letter": {
+            "type": "string"
+          },
+          "executor": {
+            "description": "name, rating, completed_tasks of the human",
+            "type": "object"
+          },
+          "id": {
+            "description": "Application UUID, use with accept/reject/review",
+            "type": "string"
+          },
+          "result_file_url": {
+            "description": "Photo/file URL, present after submission",
+            "type": "string"
+          },
+          "result_text": {
+            "description": "Present after the human submits",
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "pending",
+              "accepted",
+              "revision",
+              "submitted",
+              "approved",
+              "rejected"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "reward": {
+      "type": "number"
+    },
+    "status": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "applications"
+  ],
+  "type": "object"
+}

First observedJun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark this as read-only, open-world, and idempotent. The description adds that results evolve with new applications and submissions, aligning with 'openWorldHint'. No contradictions.

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?

Two sentences efficiently convey purpose and usage without redundancy. Front-loaded with key details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description covers essential fields and usage context. No gaps for this simple get operation.

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% with 'task_id' described as 'Task UUID', which is sufficient. The description does not add extra semantic meaning to the parameter, earning baseline score.

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 tool retrieves task details including all human applications with specific fields, distinguishing it from sibling tools like 'list_tasks' (list vs. details) and 'accept_application' (action vs. retrieval).

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 explicitly recommends using this tool to poll for new applications and submitted results, providing clear context. It does not explicitly list when not to use it, but the purpose is well-defined.

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?