Skip to main content
Glama

Conductor Relay MCP

by io.github.Zman504
OverviewAdmin

Create Worker Delegation

create_worker_delegation
Idempotent

Execute the canonical Direct Session create_worker_delegation operation. Requires an Authorization: Bearer header.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nonceYesCanonical nonce argument for the create_worker_delegation Direct Session operation.
scopesYesCanonical scopes argument for the create_worker_delegation Direct Session operation.
worker_idYesCanonical worker id argument for the create_worker_delegation Direct Session operation.
expires_atYesCanonical expires at argument for the create_worker_delegation Direct Session operation.
token_hashYesCanonical token hash argument for the create_worker_delegation Direct Session operation.
max_spend_cptmYesCanonical max spend cptm argument for the create_worker_delegation Direct Session operation.
idempotency_keyYesRequired mutation idempotency key, shared across REST, MCP, and A2A.
allowed_offer_idsNoCanonical allowed offer ids argument for the create_worker_delegation Direct Session operation.
max_concurrent_sessionsYesCanonical max concurrent sessions argument for the create_worker_delegation Direct Session operation.
max_requests_per_minuteYesCanonical max requests per minute argument for the create_worker_delegation Direct Session operation.
allowed_provider_agent_idsNoCanonical allowed provider agent ids argument for the create_worker_delegation Direct Session operation.
ephemeral_ed25519_public_keyNoCanonical ephemeral ed25519 public key argument for the create_worker_delegation Direct Session operation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue when the upstream exchange call succeeded (HTTP status < 400).
dataYesCanonical create_worker_delegation result. Null when ok is false.
errorYesIn-band error code or message when ok is false; null on success.
statusYesUpstream HTTP status code returned by the Conductor Relay API.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changed
    • addedInput schema / properties / allowed_offer_ids / description
      Added value: +"Canonical allowed offer ids argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / allowed_provider_agent_ids / description
      Added value: +"Canonical allowed provider agent ids argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / ephemeral_ed25519_public_key / description
      Added value: +"Canonical ephemeral ed25519 public key argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / expires_at / description
      Added value: +"Canonical expires at argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / max_concurrent_sessions / description
      Added value: +"Canonical max concurrent sessions argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / max_requests_per_minute / description
      Added value: +"Canonical max requests per minute argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / max_spend_cptm / description
      Added value: +"Canonical max spend cptm argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / nonce / description
      Added value: +"Canonical nonce argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / scopes / description
      Added value: +"Canonical scopes argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / token_hash / description
      Added value: +"Canonical token hash argument for the create_worker_delegation Direct Session operation."
    • addedInput schema / properties / worker_id / description
      Added value: +"Canonical worker id argument for the create_worker_delegation Direct Session operation."
  2. Added

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already indicate a non-read-only operation (readOnlyHint=false), and the description adds the requirement for a Bearer token. However, it does not disclose what the operation does behaviorally, such as side effects, idempotency implications, or what a created delegation entails. The added value over annotations is minimal.

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?

The description is a single sentence with no wasted words, making it concise and front-loaded. However, its extreme brevity comes at the cost of missing critical purpose and usage information, so it is not ideal but structurally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters and 9 required fields, the description is grossly incomplete. It does not explain what a worker delegation is, when to use it, or how it relates to sibling tools like revoke_worker_delegation. Even with an output schema present, the description leaves the agent without sufficient context to invoke the tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description itself adds no parameter semantics, but the schema fully lists all parameters. However, most schema descriptions are formulaic ('Canonical ... argument') and add little real meaning, yet the tool description does not compensate for this.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name ('create_worker_delegation operation') without explaining what a worker delegation is or what creating one accomplishes. It does not distinguish this tool from siblings beyond its name, leaving the purpose vague and tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. The description only mentions the Authorization header requirement, which is a necessary condition but not a usage guideline. No scenarios, exclusions, or comparative context are provided.

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

All Conductor Relay MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources