Skip to main content
Glama

workman.rent — humans for real-world checks

Poll pairing status; returns client_id + api_key ONCE

pairing_status

Step 2 of onboarding. While pending returns { status }. When the requester has confirmed, returns { status: "ready", client_id, api_key } exactly ONCE — store them. Then reconnect to https://workman.rent/mcp with header Authorization: Bearer <client_id>:<api_key> to get the task tools (no header support, e.g. Claude.ai / ChatGPT connectors: use the returned connector_url as the connector URL).

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": {
      "code": "<code>"
    },
    "name": "pairing_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPairing code from start_pairing

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 readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false; they say nothing about the critical behavior here. The description adds the decisive fact that client_id and api_key are returned exactly ONCE and must be stored — a lossy, non-repeatable side effect an agent could not infer. It also explains the follow-up reconnection requirement, which is the real behavioral consequence of this call.

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 step position and the returned shapes, then the operational follow-up. It is dense and slightly run-on (the header and connector_url guidance are crammed into one sentence), but nearly every clause is operationally necessary 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, so the description correctly carries the full burden of describing return values, and it does so for both the pending and ready states. Combined with the one-time credential warning and the next-step connection instructions, an agent has everything needed to call this correctly and act on the result.

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?

There is a single parameter with 100% schema description coverage ('Pairing code from start_pairing'), so the schema already carries the semantics. The description adds no format, length, or sourcing detail for `code` beyond that, which is the expected baseline when the schema does the work.

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+resource (poll pairing status) and immediately positions it as 'Step 2 of onboarding', which sequences it after start_pairing without ambiguity. It also spells out the two possible return shapes ({ status } vs { status: "ready", client_id, api_key }), so an agent knows exactly what the call yields.

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 explicit when-to-use conditions: call it while the requester is pending, and call it to collect credentials once confirmation happens. It goes further than most definitions by describing the post-call action (reconnect with the Authorization header) and a named fallback path for clients without header support (use connector_url), leaving no routing decision to inference.

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