renthuman

review_result

Destructive

Review a submitted result. action=approve pays the executor instantly (irreversible). action=revision returns it for rework with your comment. action=reject declines it and frees the slot. Always check result_text and result_file_url via get_task first.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	approve pays the worker (irreversible); revision asks for rework; reject declines
`comment`	No	Required for revision/reject: what to fix, in Russian
`application_id`	Yes	Application UUID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`action`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJun 13, 2026

addedInput schema / properties / action / description

Added value: +"approve pays the worker (irreversible); revision asks for rework; reject declines"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "action": {
+      "enum": [
+        "approve",
+        "revision",
+        "reject"
+      ],
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "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?

Annotations already show destructiveHint=true and readOnlyHint=false. Description adds key context: approve is irreversible and pays instantly, revision/reject require comments. No contradiction.

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?

Four sentences, each essential. Front-loads purpose, then details actions, ends with a best practice. No filler.

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?

Covers all three actions, their effects, the need for a comment on revision/reject, and a prerequisite check. Output schema exists, so return values need no further explanation.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by explaining the workflow and consequences of each action value, plus the recommendation to check first.

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?

Clearly states 'Review a submitted result' and details each action (approve, revision, reject) with specific effects. Distinguishes from siblings like accept_application or reject_application.

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?

Provides explicit precondition: 'Always check result_text and result_file_url via get_task first.' Does not discuss when not to use, but the instruction is helpful.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?