Skip to main content
Glama

assign_worker

Hire the applicant that will do the job. Needs a write key and an idempotencyKey. Name the mandateId you posted with (list_mandates shows yours). On this sandbox door pass the write key from get_sandbox_key as the apiKey argument.

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": {
      "jobId": "<jobId>",
      "workerId": "<workerId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "assign_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
apiKeyNoYour key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key.
workerIdYes
mandateIdNo
idempotencyKeyYesRequired on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotencyKey / description
      Added value: +"Required on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call."
  2. Changed1 schema field changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"The key from register_agent, for MCP clients that cannot send an Authorization header. Accepted for the registration key (read + exam); a key that can write must be sent as the Authorization header."New value: +"Your key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key."
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, closed-world write action, so the safety profile is partly covered. The description usefully adds the auth requirement (write key) and the sandbox apiKey routing, but says nothing about downstream effects such as escrow/funding, reversibility, or what a successful hire changes.

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?

Three short sentences, front-loaded with the action and followed by prerequisites in the order an agent needs them. Nothing is padded, though the phrasing is terse enough that "that will do the job" adds little information.

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?

With no output schema and a mutation action, the definition should say more about the result and side effects of hiring. It covers auth, idempotency, and the mandate linkage well enough to call the tool, but leaves the outcome and state transition opaque.

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 only 40%, yet the description explains three of the five parameters: mandateId (name the mandate you posted with, list_mandates shows yours), apiKey (the sandbox write key from get_sandbox_key), and idempotencyKey (required). jobId and workerId remain unexplained, but the description clearly compensates for most of the coverage gap.

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?

"Hire the applicant that will do the job" names a concrete verb (hire/assign) and resource (applicant/worker), which is distinct from sibling flows like apply_job or list_applicants. It is clear what the tool does, though it never explicitly contrasts itself with a named alternative.

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?

The definition supplies real preconditions: a write key, an idempotencyKey, and the mandateId from the earlier post_job step, with list_mandates and get_sandbox_key named as the sources. It gives clear invocation context but no exclusions or when-not-to-use guidance.

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