Skip to main content
Glama

Decide pending action

decide_pending_action
Destructive

Approve or reject one AI action parked for a human decision (the twin of ankra chat actions confirm|reject), or every action of one batch at once by its batch_id (the actions one session parked together, shown beside each action by list_pending_actions), for MCP clients acting on behalf of an organisation admin. Only organisation admins, and the policy's designated approvers when it names any, may decide; approving resumes the session that proposed the action and executes the change it parked, rejecting tells it not to. Read the action with list_pending_actions first and say plainly what approving will change. Refused once the action is already decided or expired. Over MCP or any API token the decision needs a token whose scopes name ai_actions.approve: mcp:write alone is refused (error_code AI_ACTION_APPROVAL_NEEDS_HUMAN_PERMISSION). On a protected target (a stack under an enabled backup policy, or a production cluster) the person who configured the remediation policy, or whose identity the proposing lane runs as, cannot approve; another admin must (error_code AI_ACTION_SELF_APPROVAL_ON_PROTECTED_TARGET); that self-approval rule never restricts rejecting. Not offered in chat: there, the parked action's own card is the decision.

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": {
      "decision": "<decision>"
    },
    "name": "decide_pending_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idNoThe batch id (UUID) from list_pending_actions, to decide every live action of the batch at once. Name this or action_id, not both.
decisionYesApprove runs the parked change; reject discards it.
action_idNoThe pending action id (UUID) from list_pending_actions. Name this or batch_id, not both.
action_idsNoWith batch_id and decision approve: the action ids (UUIDs) to approve; the batch's other live actions are rejected. Omit to approve them all. Not allowed with reject, which settles the whole batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / action_id / description
      Previous value: -"The pending action id (UUID) from list_pending_actions."New value: +"The pending action id (UUID) from list_pending_actions. Name this or batch_id, not both."
    • addedInput schema / properties / action_ids
      Added value: +{
      +  "description": "With batch_id and decision approve: the action ids (UUIDs) to approve; the batch's other live actions are rejected. Omit to approve them all. Not allowed with reject, which settles the whole batch.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / batch_id
      Added value: +{
      +  "description": "The batch id (UUID) from list_pending_actions, to decide every live action of the batch at once. Name this or action_id, not both.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "action_id",
      -  "decision"
      -]New value: +[
      +  "decision"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructive=true and readOnly=false, and the description adds substantial context beyond them: approving resumes the proposing session and executes the parked change, reject discards it, calls are refused once the action is decided or expired. It further discloses the required token scope (ai_actions.approve) and the self-approval prohibition on protected targets with concrete error codes, which the annotations cannot convey.

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 decision semantics before permissions and edge cases, and every clause carries operational information. It is dense and parenthetical-heavy, and a few clauses (the CLI twin reference) add little for an agent, but nothing is filler.

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?

For a destructive, permission-gated mutation with no output schema, the description covers who may call it, what each decision does, the token scope required, the self-approval carve-out, and the failure states. An agent has everything needed to call it correctly or refuse to.

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 the baseline is 3; the description still adds meaning by explaining that a batch_id is the set of actions one session parked together and that the ids come from list_pending_actions. The approve-subset semantics of action_ids are largely already in the schema, so this is incremental rather than decisive.

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?

Names a specific verb pair and resource ('Approve or reject one AI action parked for a human decision'), and scopes it further to single action, batch, or subset. It explicitly distinguishes itself from the sibling read tool (list_pending_actions) and from the in-chat path, so an agent can route without opening schemas.

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 an explicit precondition sequence ('Read the action with list_pending_actions first and say plainly what approving will change') and an explicit exclusion ('Not offered in chat: there, the parked action's own card is the decision'). It also states the eligibility conditions (organisation admins, designated approvers) that gate use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.