Skip to main content
Glama

Approval Manage Tool

approval_manage
Destructive

Manage human-in-the-loop approvals: list pending requests, approve or reject decisions, complete human tasks with form data, and configure webhook notifications. Unblocks workflow steps gated on reviewer decisions.

Instructions

Human-in-the-loop approvals and workflow human-task completion. Use this to unblock workflow steps gated on reviewer decisions or to submit form data for human_task DAG nodes. Each decision is audit-logged and emits a domain event the workflow runtime listens for.

Actions:

  • list (read) — optional: status (pending/approved/rejected/expired), assignee_id, limit.

  • approve (write) — approval_id, optional comment. Unblocks the dependent step.

  • reject (write) — approval_id, reason. Terminates the dependent step (workflow may branch on rejection).

  • complete_human_task (write) — approval_id, form_data (JSON matching the node's form_schema). Validates against the schema before commit.

  • webhook_config (write) — approval_id, webhook_url. Configures external notification when status changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list, approve, reject, complete_human_task, webhook_config
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
statusNoFilter by status: pending, approved, rejected, expired (default: pending)pending
limitNoMax results to return (default 10, max 100)
approval_idYesThe approval request UUID
notesNoOptional reviewer notes
reasonYesReason for rejection
form_responseYesThe form response data as key-value pairs matching the form_schema fields
callback_urlNoHTTPS URL to POST the decision payload to (set to null to clear)
callback_secretNoSecret used to sign the payload via HMAC-SHA256 (X-Signature-SHA256 header)
Behavior5/5

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

Adds detail beyond destructiveHint annotation: audit-logging, domain events, and action consequences (approve unblocks, reject terminates). No contradiction with annotations.

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?

Efficient structure: opening sentence defines purpose, then bullet points for each action with parameter details. No wasted words.

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?

Despite 10 parameters, no output schema, and multiple actions, the description covers all necessary context: when to use, per-action parameters, outcomes, and side effects. Agent can correctly select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline 3, but description adds meaning by associating parameters with specific actions and clarifying usage (e.g., comment optional for approve, reason required for reject, form_data must match schema). Overcomes schema's over-required fields.

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?

Clearly defines tool as managing approvals and human-task completion. Explicitly lists actions (list, approve, reject, complete_human_task, webhook_config) and their effects, distinguishing from sibling manage tools.

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?

States when to use: unblock workflow steps or submit form data for human_task DAG nodes. Describes effects of each action but does not explicitly mention alternatives or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/escapeboy/agent-fleet-o'

If you have feedback or need assistance with the MCP directory API, please join our Discord server