Skip to main content
Glama

execute_after_approval

Resume execution of a controlled action after principal approval by providing the audit id, approval id, action, resource, and environment.

Instructions

Resume a controlled action after principal approval.

The approval payload key is `approval_id`. This tool deliberately passes
that key through to `AVPAgent.execute_after_approval(...)`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audit_idYesRuntime Gate audit_id from the WAITING_FOR_HUMAN_APPROVAL decision
approval_idYesApproved human approval id. Use approval.approval_id, not approval.id
actionYesAction name bound to the Runtime Gate decision
resourceYesResource identifier bound to the Runtime Gate decision
environmentYesExecution environment bound to the Runtime Gate decision
paramsNoOptional execution params as a JSON object string. Default: {}{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It only mentions passing through the approval key, omitting side effects, error conditions, or idempotency. Minimal behavioral disclosure.

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, direct sentences with no fluff. Purpose is front-loaded and every word adds value.

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

Completeness2/5

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

Despite an output schema being present, the description fails to explain what the tool returns or any execution context. Lacks guidance on error handling or confirmation of success.

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?

Input schema has 100% coverage with descriptions for all 6 parameters, so description adds negligible value. Baseline 3 is appropriate.

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 states it resumes a controlled action after approval, referencing the approval payload key. Distinguishes itself from siblings like 'approve_action' or 'controlled_action' by specifying the resume behavior.

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?

Implies usage for resuming after approval but lacks explicit when-to-use vs. alternatives or exclusions. No mention of when not to use or prerequisites.

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/agentveil-protocol/avp-sdk'

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