Skip to main content
Glama

workman.rent — humans for real-world checks

Get a SANDBOX key, step 2: email code → client_id + sk_sandbox_ key

sandbox_signup_verify

Confirms the 6-digit code and returns { client_id, api_key: "sk_sandbox_…" } ONCE — store them. Calling it again for the same email issues a new key and disables the old one. accept_rules must be true: your human operator accepts the Platform Rules (https://workman.rent/oferta.html) — ask them before you send it. Then reconnect to https://workman.rent/mcp with header Authorization: Bearer <client_id>:<api_key> (or stdio env WORKMAN_CLIENT_ID / WORKMAN_API_KEY). Client cannot set headers (Claude.ai / ChatGPT custom connector)? Use the returned connector_url as the connector URL. Returns: { sandbox: true, client_id, api_key, connector_url, limits, quickstart, go_live }

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>",
      "code": "<code>",
      "accept_rules": "<accept_rules>"
    },
    "name": "sandbox_signup_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes6-digit code from the email
emailYesSame email as in sandbox_signup_start
accept_rulesYestrue = your human operator accepted the Platform Rules

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly=false, idempotent=false, openWorld=true. The description goes well beyond them: credentials are returned once and must be stored, repeated calls rotate and invalidate the previous key, accept_rules must be true, and there is a fallback for clients that cannot set custom headers via connector_url. This is exactly the operational context an agent needs to avoid destroying its own working key.

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?

Dense and front-loaded — the one-time-return and key-rotation warning comes first, then the consent prerequisite, then the reconnection mechanics, then the return shape. It is longer than typical but nearly every clause carries operational information; the header-format and env-var details could be tightened 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 credential-issuing tool with no output schema, the description supplies the return payload keys, the one-time retrieval semantics, the consent precondition, and what to do with the credentials afterward. Nothing an agent needs to call this correctly and not lose its key 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?

Schema coverage is 100%, so the schema already documents all three parameters and the baseline would be 3. The description still adds meaning: accept_rules is tied to a named external document and framed as consent the human must give before the call, which is more actionable than the schema's one-line const description.

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 — confirms the 6-digit email code and returns { client_id, api_key } — and labels itself "step 2" of the signup flow, making its relationship to sandbox_signup_start unambiguous without opening either 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?

Explicitly covers when to use (after receiving the emailed code), when not to re-use (calling again for the same email issues a new key and disables the old one), and a precondition that must happen before sending (a human operator must accept the Platform Rules). The post-call reconnection path is also spelled out.

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