Skip to main content
Glama

clear_human_gate

DestructiveIdempotent

Releases an agent-armed human gate on a task when the gate’s clear path is an endpoint; it refuses marker-based gates that require a withdrawal comment.

Instructions

Release a human gate. human_gate_info on get_task(full=true) reports clear_path. clear_path="clear_endpoint" means YOU armed this gate through set_human_gate and it carries no marker comment — this tool releases it, and a withdrawal comment would be a silent no-op. clear_path="withdraw_marker" means the ask lives in a "Blocking @" comment: this tool refuses, and the gate is taken down by a short negator comment. Everything else is user-only — a gate a human armed, or one raw-armed via PATCH/UI with no author — and an agent key gets a 403 naming the exit it CAN reach: a human-gate decision records the human's answer. A posted comment does not by itself clear the gate; human_gate on get_task shows the current state.

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": {
      "task_id": "<task_id>"
    },
    "name": "clear_human_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID whose gate to clear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag destructive+idempotent; the description adds far more: the tool refuses rather than no-ops under withdraw_marker, a withdrawal comment here is a silent no-op, agent keys get a 403 on user-owned gates, and a posted comment does not by itself clear the gate. These are exactly the failure modes an agent would otherwise hit blind.

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-loaded with the action, then the branch table. It is dense and jargon-heavy (clear_endpoint / withdraw_marker / negator comment) in one unbroken block, but every clause carries routing information rather than filler.

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?

Covers the state-dependent behavior, refusal semantics, and where to inspect current gate state (human_gate on get_task), which is a lot for a one-param mutation with no output schema. It stops short of saying what a successful release returns or how the task's blocking state changes.

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?

Single parameter with 100% schema description coverage, so the schema already defines task_id as "Task ID whose gate to clear." The description adds no format, sourcing, or precondition detail beyond it. Baseline 3 applies.

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?

Opens with a specific verb+resource ("Release a human gate") and immediately frames the tool against its counterpart set_human_gate and against the raw-armed / human-armed variants. An agent can tell exactly which gate population this applies to without reading 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 Guidelines5/5

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

Gives explicit conditional routing: clear_path="clear_endpoint" means use this tool; clear_path="withdraw_marker" means it refuses and a negator comment is the correct action; anything else is user-only and yields a 403 naming an alternative. This is a when/when-not/alternative triad stated as fact, not inference.

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