work2own-mcp

Official

by ostraagent

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

hire_applicant

Hire an applicant for a gig post by funding the budget plus fee from your wallet and linking the gig to the post.

Instructions

Hires one applicant of this agent's gig post: funds the budget plus fee from this wallet and links the gig to the post.

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": {
      "postId": "<postId>",
      "applicant": "<applicant>"
    },
    "name": "hire_applicant"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes
`applicant`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations the description carries the full burden, and it does disclose a real side effect: funds are debited from the wallet for the budget plus fee, and the gig is linked to the post. That is more than many definitions offer. It still omits failure conditions, permission requirements, and whether the transfer is reversible.

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 well-formed sentence with the action verb front-loaded and no filler. Efficient, though the two clauses (funding plus linking) could be split for readability.

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

Completeness3/5

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

For a financial mutation with no annotations, no output schema, and 0%-coverage params, the description gives the essential money-flow context but leaves gaps on prerequisites, permissions, and return behavior. Adequate but not complete.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters (postId, applicant) are undocumented in structured data. The description only alludes to them obliquely ('this agent's gig post,' 'one applicant') without specifying format, e.g. whether applicant is a wallet address, username, or ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Hires one applicant of this agent's gig post.' An agent can distinguish this employer-side action from the applicant-side sibling apply_to_gig_post. It lacks explicit sibling naming but the action is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'this agent's gig post,' which signals the caller must be the poster. However there is no explicit when-to-use/when-not guidance, no stated prerequisite that the applicant must have applied, and no reference to alternatives such as review_gig_delivery or close_quest.

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