Skip to main content
Glama
profilesearch

GoHireHumans

Official
by profilesearch
OverviewSchemaSourceRelated ServersDiscussionsAdmin

release_payment

Destructive

Approve a worker's submitted work on an order and release their payout. Irreversible; requires employer auth and order status 'submitted'.

Instructions

Approve the worker's submitted work on an order and release their payout. This pays the worker and cannot be undone, so only call it after the account owner has reviewed the delivered work and explicitly approved payment. Must be called as the order's employer with GOHIREHUMANS_AUTH_TOKEN; unset GOHIREHUMANS_API_KEY first, because API-key authentication isn't supported for this action and a valid API key is rejected even alongside the session token. The order must be in 'submitted' status (check with get_job_status). Approves the order's current submitted milestone; where checkout is configured, Stripe releases the worker's listed payout. If the order has another milestone, the employer's saved card is charged for it at the same time. After the last milestone the order is completed and can be reviewed with submit_review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratingNoNot recorded by this tool; rate the worker with submit_review after the order completes. Kept for backward compatibility.
order_idYesID of the order whose submitted work you are approving
milestone_idNoIgnored: the API always approves the order's current submitted milestone. Kept for backward compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / properties / milestone_id / description
      Previous value: -"Optional specific milestone ID to release payment for. If not specified, releases payment for the entire order."New value: +"Ignored: the API always approves the order's current submitted milestone. Kept for backward compatibility."
    • changedInput schema / properties / order_id / description
      Previous value: -"The order ID for which to release payment"New value: +"ID of the order whose submitted work you are approving"
    • changedInput schema / properties / rating / description
      Previous value: -"Optional rating (1-5) to submit along with payment release"New value: +"Not recorded by this tool; rate the worker with submit_review after the order completes. Kept for backward compatibility."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=false, but the description adds substantial non-structured context: the action is irreversible, it requires GOHIREHUMANS_AUTH_TOKEN while the API key must be unset because API-key auth is rejected, Stripe releases the payout where checkout is configured, and the saved card is charged for a following milestone. This is far beyond what the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and its irreversible nature, then layers auth, status, and milestone mechanics. It is dense and multi-clause, but every sentence carries operational value; the auth-requirement sentence is the longest and slightly heavy.

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?

For a destructive, non-idempotent payment tool with no output schema, the description covers irreversibility, auth requirements, preconditions, downstream effects on milestones/Stripe, and what to do after the final milestone. Nothing an agent needs to call it safely is missing.

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% and the schema itself explains that rating and milestone_id are ignored/legacy. The description adds no per-parameter detail, but with full schema coverage the baseline of 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?

States a specific verb pair (approve + release payout) on a specific resource (the worker's submitted work on an order). An agent can distinguish this from siblings like get_job_status or submit_review without opening any schema.

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?

Gives explicit preconditions (only after the owner has reviewed and approved), required order status ('submitted'), the alternative to check status (get_job_status), and the follow-up tool for rating (submit_review). Routing and when-not-to-call are both covered.

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

Deploy Server

Other Tools