Skip to main content
Glama

workman.rent — humans for real-world checks

Get a pairing code (onboarding, no account needed)

start_pairing

Step 1 of onboarding. Returns a short code (valid 15 min). Show it to your human operator: a VERIFIED requester confirms it in the dashboard at https://workman.rent/zamovnik.html. Then call pairing_status with the code. There is no anonymous self-registration. No verified requester yet? Try the SANDBOX first (sandbox_signup_start): full task flow with a bot, no verification. Returns: { code, expires_in, poll_after, instruction }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_pairing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only flag it as non-read-only, open-world, and non-idempotent. The description adds the traits that actually matter: the code expires in 15 minutes, a human-in-the-loop verified requester must confirm it in a dashboard at a specific URL, and there is no anonymous fallback. That is substantially more than the structured fields provide.

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?

Front-loaded with the step position and the returned artifact, then the required human action, then the next call, then the alternative path. Every sentence contributes a distinct decision-relevant fact, and the return shape is compactly listed at the end.

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 zero-parameter, no-output-schema onboarding step, the description covers everything an agent needs: expiry window, the external human confirmation requirement, the correct next tool, and the fallback path. Nothing essential is missing.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to add. The description instead documents the return shape (code, expires_in, poll_after, instruction), which compensates for the absence of an output schema.

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 and resource: returns a short pairing code valid 15 minutes as step 1 of onboarding. It is immediately distinguishable from pairing_status (the follow-up) and sandbox_signup_start (the alternative path), so an agent can identify it 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 the full sequence: call this, show the code to a human operator, then call pairing_status with the code. It also names an explicit alternative (sandbox_signup_start) with the condition that selects it — no verified requester yet — and states that anonymous self-registration is not possible.

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