Skip to main content
Glama

impri_await_decision

Poll until a human approves or rejects a pending action, or timeout elapses. Returns the decision to proceed, abort, or retry.

Instructions

Poll until the human approves, rejects, or the timeout elapses.

Checks GET /actions/:id every 5 seconds and returns as soon as the action leaves the pending state.

Decision meanings: "approved" — proceed with the action; any reviewer edits are included in preview/payload "rejected" — abort; respect the decision and do not proceed "expired" — the approval window closed; create a new action if the task is still relevant

On timeout the action stays pending in the inbox. Call impri_inbox_status to check queue depth and consider pausing further submissions.

Typical usage:

  1. impri_push_action → get action_id

  2. impri_await_decision(action_id) → wait for human decision

  3. If approved: execute the action, then impri_report_result(action_id, "executed")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
action_idYesThe id returned by impri_push_action.
timeout_sNoMaximum seconds to wait before returning (default 300 — 5 minutes). After timeout the action is still pending; retry or call impri_inbox_status.
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses polling interval (5 seconds), decision meanings (approved, rejected, expired), timeout behavior (stays pending), and suggests follow-up calls. No contradictions.

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?

Well-structured: summary first, then details on polling, decisions, timeout, and typical usage. Every sentence adds value, no redundancy, and front-loaded.

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?

Given complexity (polling, multiple outcomes, workflow integration) and no output schema, the description is complete. Covers what, when, how to interpret, and what to do on timeout.

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% (baseline 3). Description adds meaning: action_id is 'returned by impri_push_action' and timeout_s explains default (300s) and behavior after timeout. This goes 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 'Poll until the human approves, rejects, or the timeout elapses.' The verb 'poll' and resource 'human decision' are specific. It distinguishes from siblings like impri_push_action (push action) and impri_inbox_status (queue depth).

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?

Provides a 'Typical usage' sequence (push → await → execute/report) and alternatives on timeout (impri_inbox_status). Clearly tells when to use and when not to (after push, before execution).

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/sekera-radim/impri'

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