Quorus

Official

Overview Schema Source Related Servers Discussions Admin

release_task

Release a file lock in a shared Quorus room using the lock token from claim_task, so other coding agents can access or claim that file.

Instructions

Release a file lock. Requires the lock_token from claim_task.

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": {
      "room_id": "<room_id>",
      "file_path": "<file_path>",
      "lock_token": "<lock_token>"
    },
    "name": "release_task"
  }
}

Input Schema

Name	Required	Description	Default
`room_id`	Yes
`file_path`	Yes
`lock_token`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Oct 18, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about idempotency, behavior on an invalid or stale lock_token, required permissions, whether an error is returned, or whether releasing affects any other held state. For a mutation operation with zero annotation coverage this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no padding, and the action is front-loaded ahead of the prerequisite. Every clause earns its place.

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?

An output schema exists, so return values need not be explained. Still, for an unannotated mutation tool the description omits error and idempotency behavior, and two input parameters are undocumented, leaving the agent underinformed despite the useful prerequisite hint.

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 0%, so the description must compensate. It adds real meaning for lock_token by identifying its origin (claim_task), but room_id and file_path remain entirely undocumented, leaving two of three parameters unexplained. Partial compensation only.

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 and resource: 'Release a file lock.' It also names the related tool (claim_task), which helps distinguish it from siblings even though the naming mismatch between 'release_task' and 'file lock' requires the reader to reconcile the two. Clear enough to act on 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 Guidelines3/5

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

The line 'Requires the lock_token from claim_task' implies this is only used after a successful claim, which is useful sequencing guidance. However, it never states when not to use it, what happens if the lock was already released, or how it relates to other lock-affecting tools.

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