Skip to main content
Glama
profilesearch

GoHireHumans

Official
by profilesearch
OverviewSchemaSourceRelated ServersDiscussionsAdmin

submit_review

Submit a 1-5 star rating and written review for the other party on a completed GoHireHumans order. Requires auth token and order completion.

Instructions

Leave a 1-5 star rating and written review for the other party on a completed order: the employer reviews the worker and the worker reviews the employer. Needs GOHIREHUMANS_AUTH_TOKEN or an API key with the write scope, from an account that is part of the order, and the order must be completed. Each participant can review an order once, and reviews can't be edited or deleted through the API. A review stays hidden until both parties have reviewed or 14 days have passed since completion; then it appears publicly on the reviewed person's profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratingYesOverall rating from 1 to 5 stars; shown publicly once the review is visible
commentYesWritten review of the other party's work or conduct; shown publicly once the review is visible
order_idYesID of the completed order to review
quality_ratingNoOptional quality sub-rating (1-5). Accepted but not currently stored or shown.
timeliness_ratingNoOptional timeliness sub-rating (1-5). Accepted but not currently stored or shown.
communication_ratingNoOptional communication sub-rating (1-5). Accepted but not currently stored or shown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • changedInput schema / properties / comment / description
      Previous value: -"Written review of the worker's performance"New value: +"Written review of the other party's work or conduct; shown publicly once the review is visible"
    • changedInput schema / properties / communication_rating / description
      Previous value: -"Communication rating (1-5)"New value: +"Optional communication sub-rating (1-5). Accepted but not currently stored or shown."
    • changedInput schema / properties / order_id / description
      Previous value: -"The order ID to review"New value: +"ID of the completed order to review"
    • changedInput schema / properties / quality_rating / description
      Previous value: -"Quality of work rating (1-5)"New value: +"Optional quality sub-rating (1-5). Accepted but not currently stored or shown."
    • changedInput schema / properties / rating / description
      Previous value: -"Rating from 1 to 5 stars"New value: +"Overall rating from 1 to 5 stars; shown publicly once the review is visible"
    • changedInput schema / properties / timeliness_rating / description
      Previous value: -"Timeliness/delivery speed rating (1-5)"New value: +"Optional timeliness sub-rating (1-5). Accepted but not currently stored or shown."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description goes well beyond them: reviews cannot be edited or deleted via API, one per participant per order, auth scope requirements, and a hidden-until-both-reviewed-or-14-days visibility rule. This is unusually rich operational context and it is consistent with (not contradicting) the annotations.

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?

A single dense paragraph that front-loads what the tool does before layering conditions. Every clause (auth, completion, once-only, immutability, visibility delay) carries distinct information, though the sentence count could be trimmed slightly.

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 6-param mutation with no output schema, the description supplies everything an agent needs: preconditions, auth requirements, cardinality limits, immutability, and post-submission visibility behavior. Nothing material 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%, so all six parameters including the odd 'accepted but not stored' sub-ratings are already documented in the schema. The description restates the 1-5 rating and written review but adds only the visibility timing, so 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?

States a specific verb (submit/leave) and resource (a 1-5 star rating and written review) on a clearly bounded target (a completed order, other party). It even clarifies the two directions (employer reviews worker, worker reviews employer), so an agent knows exactly what this produces.

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?

Gives explicit preconditions: auth token or write-scoped API key, account must be part of the order, order must be completed, and each participant may review once. No sibling tool overlaps this function, so the absence of named alternatives is not a real gap.

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