callable

review_task

Idempotent

Optional. Approve or dispute a task that is in pending_review status. Use this after get_task_status reports the operator has completed the work. Approving releases the operator payout. Disputing requires a reason and a description of what is needed for acceptance; the operator is then allowed to resubmit. If you never call review_task, tasks are auto-approved after the review window expires.

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>",
      "decision": "<decision>"
    },
    "name": "review_task"
  }
}

Input Schema

Name	Required	Description
`task_id`	Yes	The task ID returned by submit_task.
`decision`	Yes	approve to accept the result and release payment; dispute to reject it and request a resubmission.
`dispute_reason`	No	Required when decision = 'dispute'. What went wrong with the submission.
`what_is_needed`	No	Required when decision = 'dispute'. What the operator must do for the submission to be accepted.

Output Schema

Name	Required	Description	Default
`status`	Yes
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations (which already indicate non-read-only and idempotent), the description discloses important effects: 'Approving releases the operator payout,' 'Disputing... the operator is then allowed to resubmit,' and the auto-approval fallback. These are behavioral consequences not captured by the annotations or schema.

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 four sentences, front-loaded with the core action. Every sentence earns its place: the action, the trigger, the effects, and the fallback behavior. No redundant or tangential information.

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 an output schema exists, the description need not explain return values. It covers when to call, what actions do, required fields for dispute, and the auto-approval safety net. This is sufficient for an agent to select and invoke the tool correctly in a workflow.

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 schema already provides 100% coverage for all four parameters, including descriptions and the conditional requirement for dispute_reason/what_is_needed. The tool description adds contextual consequences (e.g., 'releases payout') but does not introduce new parameter-level semantics beyond what the schema states. Baseline 3 is appropriate.

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's purpose: 'Approve or dispute a task that is in pending_review status.' It uses a specific verb and resource, and distinguishes itself from siblings by saying 'Use this after get_task_status reports the operator has completed the work,' positioning it as the follow-up action to a status check.

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

Usage Guidelines5/5

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

Provides explicit usage context: 'Use this after get_task_status reports the operator has completed the work.' It also explains the alternative of not calling the tool ('tasks are auto-approved after the review window expires'), which helps the agent decide if invocation is needed.

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

All callable 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?