Gumloop MCP Server

Resolve approvals

resolve_session_approvals

Destructive

Answer pending tool approvals, human input requests, and checkpoints for a paused session so the agent can resume.

Instructions

Answer pending asks on a session that is paused in the approval_required state — tool approvals, human input requests, and checkpoints.

List the pending asks with Retrieve session: each entry in pending_approvals carries the action_request_id to answer, and human_input asks include the questions to fill in via response.values. Resolutions are processed in order; the agent resumes once the pending asks are answered. Explicit confirmation is required for this exact account operation. Runs can spend credits or trigger downstream actions; never resubmit unknown outcomes automatically.

Input Schema

TableJSON Schema

Name	Required	Description
`account`	No	Named private Gumloop account; selects private credentials and user/team identity.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON request body instead of body flags. Preserves current endpoint fields and values.
`session_id`	Yes	ID of the session with pending approvals.
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`approval_responses`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv3.0.0Oct 5, 2026

addedInput schema / $defs / approval_responses

Added value: +{
+  "description": "Answers to pending asks. Each `action_request_id` may appear at most once.",
+  "items": {
+    "properties": {
+      "action": {
+        "description": "Whether to approve or reject the pending ask.",
+        "enum": [
+          "accept",
+          "reject"
+        ],
+        "type": "string"
+      },
+      "action_request_id": {
+        "description": "ID of the pending ask, from `pending_approvals` on Retrieve session.",
+        "type": "string"
+      },
+      "reason": {
+        "description": "Optional reason recorded with the resolution.",
+        "maxLength": 1000,
+        "type": "string"
+      },
+      "response": {
+        "description": "For `human_input` asks — form answers keyed by question name.",
+        "properties": {
+          "values": {
+            "description": "Map of question name to answer.",
+            "type": "object"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "required": [
+      "action_request_id",
+      "action"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / approval_responses / $ref
```
Added value: +"#/$defs/approval_responses"
```

removedInput schema / properties / approval_responses / description

Removed value: -"Answers to pending asks. Each `action_request_id` may appear at most once."

removedInput schema / properties / approval_responses / items

Removed value: -{
-  "properties": {
-    "action": {
-      "description": "Whether to approve or reject the pending ask.",
-      "enum": [
-        "accept",
-        "reject"
-      ],
-      "type": "string"
-    },
-    "action_request_id": {
-      "description": "ID of the pending ask, from `pending_approvals` on Retrieve session.",
-      "type": "string"
-    },
-    "reason": {
-      "description": "Optional reason recorded with the resolution.",
-      "maxLength": 1000,
-      "type": "string"
-    },
-    "response": {
-      "description": "For `human_input` asks — form answers keyed by question name.",
-      "properties": {
-        "values": {
-          "description": "Map of question name to answer.",
-          "type": "object"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "required": [
-    "action_request_id",
-    "action"
-  ],
-  "type": "object"
-}

removedInput schema / properties / approval_responses / maxItems
```
Removed value: -20
```
removedInput schema / properties / approval_responses / minItems
```
Removed value: -1
```
removedInput schema / properties / approval_responses / type
```
Removed value: -"array"
```

changedInput schema / properties / confirm / description

Previous value: -"Must be true for this exact requested account change, agent/flow execution, upload or deletion."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / payload / properties / approval_responses / $ref
```
Added value: +"#/$defs/approval_responses"
```

removedInput schema / properties / payload / properties / approval_responses / description

Removed value: -"Answers to pending asks. Each `action_request_id` may appear at most once."

removedInput schema / properties / payload / properties / approval_responses / items

Removed value: -{
-  "properties": {
-    "action": {
-      "description": "Whether to approve or reject the pending ask.",
-      "enum": [
-        "accept",
-        "reject"
-      ],
-      "type": "string"
-    },
-    "action_request_id": {
-      "description": "ID of the pending ask, from `pending_approvals` on Retrieve session.",
-      "type": "string"
-    },
-    "reason": {
-      "description": "Optional reason recorded with the resolution.",
-      "maxLength": 1000,
-      "type": "string"
-    },
-    "response": {
-      "description": "For `human_input` asks — form answers keyed by question name.",
-      "properties": {
-        "values": {
-          "description": "Map of question name to answer.",
-          "type": "object"
-        }
-      },
-      "type": "object"
-    }
-  },
-  "required": [
-    "action_request_id",
-    "action"
-  ],
-  "type": "object"
-}

removedInput schema / properties / payload / properties / approval_responses / maxItems
```
Removed value: -20
```
removedInput schema / properties / payload / properties / approval_responses / minItems
```
Removed value: -1
```
removedInput schema / properties / payload / properties / approval_responses / type
```
Removed value: -"array"
```

First observedv2.0.1Oct 3, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false) cover safety, and the description adds substantive context: credit spend, downstream actions, ordered processing of resolutions, and the resume-once-answered behavior. The explicit confirmation requirement maps to `confirm` and the warning about unknown outcomes is high-value operational context.

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?

Three compact sentences front-loaded with the purpose, then retrieval guidance, then safety warning. Dense but each sentence earns its place. Minor density concern but no wasted text.

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 workflow (retrieve then resolve), the ordered processing semantics, and the confirmation safety. No output schema exists; return values are not described, and the payload/payload_file alternatives are left to the schema. Adequate for a complex mutation tool with 6 params.

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?

Schema coverage is 83%, so the schema documents most parameters (action, reason, response.values, action_request_id). The description adds meaning to `action_request_id` and `response.values` sourcing and confirms the confirm/credits semantics, but doesn't clarify payload vs payload_file vs body flags alternation.

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?

States a specific verb (resolve/answer) and resource (pending asks on a paused session) with the exact precondition 'paused in the `approval_required` state'. Distinguishes its scope (tool approvals, human input, checkpoints) in a way no sibling replicates.

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?

Explicitly tells the agent to first call Retrieve session to list pending asks and where to find `action_request_id` and `questions`. Also warns not to resubmit unknown outcomes automatically. Lacks an explicit 'when NOT to use' against siblings like send_message or queue_session_message, but the prerequisite condition is clear.

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

Deploy Server

Resolve approvals

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools