Skip to main content
Glama

Release a stale Boardroom claim

release_claim
Idempotent

Safely release a stale open Boardroom todo from its current assignee so another worker can claim it.

Instructions

Safely releases a stale open Boardroom todo from its current assignee so another worker can claim it. The server refuses fresh owners, protected human/manual work, in-progress work, unassigned work, capped reclaim attempts, and rows that changed during release. agent_id required.

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": {
      "agent_id": "<agent_id>",
      "todo_id": "<todo_id>"
    },
    "name": "release_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_idYesUUID of the stale open todo claim to release
agent_idYesStable identifier for the calling agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare this as a non-read-only, idempotent, non-destructive, closed-world operation. The description adds substantial behavioral context beyond those hints: it explains the safe-release purpose and enumerates several server-side refusal conditions, including concurrency-related rejection when rows changed during release.

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 front-loaded and compact: the first sentence states purpose, and the second enumerates refusal conditions. The only minor redundancy is 'agent_id required', which is already enforced by the schema.

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

Completeness4/5

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

For an idempotent, non-destructive mutation with full schema coverage and helpful annotations, the description covers purpose and key failure conditions. It does not describe the success response, but no output schema exists and the annotations already carry the main safety profile, so this is a minor gap rather than a blocking omission.

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 both parameters are already documented as the todo UUID and stable agent identifier. The description only repeats that agent_id is required and does not add format, syntax, or semantic detail beyond the schema.

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?

The description states a specific verb and resource: releasing a stale open Boardroom todo claim from its current assignee. The scope is clear enough that an agent can distinguish this from generic todo mutation or lane-release tools without opening the schema.

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?

It gives a clear use condition (stale open Boardroom todo) and explicitly lists when the server refuses the operation, including fresh owners, protected/manual work, in-progress work, unassigned work, capped reclaims, and concurrent row changes. It does not name sibling alternatives such as claim_lane or drop_todo, so it falls short of full when/when-not/alternative guidance.

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

Deploy Server

Other Tools