Skip to main content
Glama

workman.rent — humans for real-world checks

Get a SANDBOX key, step 1 (no business verification)

sandbox_signup_start

Try workman.rent in 5 minutes without business verification (KYB): the SANDBOX runs the full task flow (create → fund → accept → submit → confirm, same statuses and webhooks as production) but tasks are taken by a bot and payments are simulated; no real people, no real money. Ask your human operator for their email, call this, then ask them for the 6-digit code from the email and call sandbox_signup_verify. Returns: { sent: true }

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": {
      "email": "<email>"
    },
    "name": "sandbox_signup_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesYour human operator's email (the code is sent there)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, open-world, non-idempotent). The description adds substantive behavior no annotation conveys: the sandbox runs the full create→fund→accept→submit→confirm flow with production-identical statuses and webhooks, but tasks are bot-taken and payments simulated. It also discloses the side effect (an email is sent) and the exact return value, { sent: true }.

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-loaded with the value proposition and sandbox semantics before the call sequence, and the Returns line is clearly delimited. The long parenthetical flow enumeration and semicolon chain make it dense, but every clause carries operational information rather than 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?

There is no output schema, and the description compensates by stating the exact return value. For a one-parameter step in a multi-step signup, the prerequisite, the side effect, the sandbox semantics, and the next tool are all covered.

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?

The single parameter is already fully documented in the schema, so the schema does the heavy lifting. The description still adds procedural meaning: the email belongs to the human operator and the verification code is delivered there, which clarifies who the value represents and what happens next.

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 action (request a sandbox signup email code) and resource (SANDBOX account), and explicitly contrasts it with production: no business verification, bot-taken tasks, simulated payments. The sandbox vs production distinction plus the step-1 framing separates it cleanly from sandbox_signup_verify.

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 a clear workflow: ask your human operator for their email, call this, then ask them for the 6-digit code and call sandbox_signup_verify. The starting condition (no KYB, sandbox trial) is explicit. It stops short of naming a production signup alternative as the when-not-to-use path, so it is strong context rather than full routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources