Skip to main content
Glama

Designate board worker

designate_board_worker
Destructive

Designate an AI agent as a board worker, or remove that designation. Only a designated agent is staffed on AI board tickets; an organisation that has designated nobody gets every ticket escalated to a human instead of worked. Identify the agent by agent_task_id or by its exact agent_name. Set board_worker false to undesignate. A designation the dispatcher would ignore is refused with the reason (a paused agent, a read-only tool_profile or autonomy_level, a one-shot mission trigger, or an agent whose runs carry no identity that can write) - fix that first, then designate. Staffing is a human-made choice, so this is confirmation-gated in chat. Unassigned board tickets are staffed on the next dispatcher cycle.

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": "designate_board_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_nameNoThe agent's exact name, as returned by list_agent_tasks.
board_workerNoTrue to designate (the default), false to undesignate.
agent_task_idNoThe agent task UUID. Optional when agent_name is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing that the call is confirmation-gated in chat, enumerating the exact refusal reasons (paused agent, read-only tool_profile or autonomy_level, one-shot mission trigger, identity-less runs), and stating that unassigned tickets are staffed on the next dispatcher cycle. That is the operational context an agent needs before mutating state.

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-loads the action and its consequence in the first two clauses, then layers preconditions. Dense but every sentence carries information; the long parenthetical refusal list makes it a single heavy paragraph rather than a crisply structured one.

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-required-parameter mutation with no output schema, the definition covers identification, the undesignate path, refusal handling, confirmation gating, and when staffing actually happens. An agent can call it correctly without consulting anything else.

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%, and the description largely restates the schema: identify by agent_task_id or exact agent_name, and board_worker=false undesignates. The 'exact agent_name' phrasing and the either/or identification hint add marginal meaning, but the schema already carries the defaults and optionality, so baseline 3 applies.

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?

States a specific verb+resource ('Designate an AI agent as a board worker, or remove that designation') and immediately explains the effect on AI board ticket staffing. It is clear what the tool does, though it never names a sibling such as provision_board_identity to sharpen the boundary.

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?

Gives strong operating context: only designated agents are staffed, an organisation with no designations escalates everything to a human, and 'Set board_worker false to undesignate' covers the inverse case. It also lists preconditions for refusal. It stops short of naming an alternative tool for cases this one rejects.

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.