Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

List pending questions

list_pending_inputs

Read-only

List an agent's paused runs awaiting human approval or input (the HITL queue) and show owners the approve URL for pending approvals. Omits requests superseded by a later completed run.

Instructions

List the agent's runs that are paused awaiting a human approval or input (the HITL queue). For an approval, show the account owner its approve_url. Only the owner can approve it in the Plori web app. A request whose session has already moved on is not listed: a later run in that conversation has completed, so answering it would resume a superseded turn.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent's UUID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pending_inputs`	Yes	Runs currently parked on a human approval or input request. A request whose session has already moved on is left out: answering it would resume a superseded turn.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.17.0Oct 1, 2026
- addedOutput schema / properties / pending_inputs / items / properties / approve_url
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "pending_inputs": {
+      "description": "Runs currently parked on a human approval or input request. A request whose session has already moved on is left out: answering it would resume a superseded turn.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "agent_id": {
+            "type": "string"
+          },
+          "args": {
+            "description": "Arbitrary JSON owned by the producing engine."
+          },
+          "connect": {
+            "additionalProperties": false,
+            "properties": {
+              "provider": {
+                "type": "string"
+              },
+              "workflow_id": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "workflow_id",
+              "provider"
+            ],
+            "type": [
+              "null",
+              "object"
+            ]
+          },
+          "consent_tool": {
+            "type": "string"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "expires_at": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "prompt": {
+            "type": "string"
+          },
+          "risk": {
+            "type": "string"
+          },
+          "run_id": {
+            "type": "string"
+          },
+          "schema": {
+            "description": "Arbitrary JSON owned by the producing engine."
+          },
+          "secret": {
+            "type": "boolean"
+          },
+          "status": {
+            "type": "string"
+          },
+          "tool_call_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "run_id",
+          "agent_id",
+          "tool_call_id",
+          "kind",
+          "prompt",
+          "status",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "pending_inputs"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the approve_url is shown to the account owner, only the owner can approve in the Plori web app, and superseded turns are silently dropped from the list.

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?

Four sentences, front-loaded with the what, followed by owner/approval mechanics and the exclusion rule. Every sentence carries information; slightly dense but no 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?

An output schema exists, so return values need no explanation. The description covers the queue definition, owner authorization, the approve_url, and the superseded-turn filter — everything an agent needs to call and interpret this correctly.

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?

There is one parameter with 100% schema description coverage ('The agent's UUID'), so the schema carries the semantics. The description adds nothing about agent_id, which is acceptable at this coverage level but no better than baseline.

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+resource with scope: runs 'paused awaiting a human approval or input (the HITL queue)'. This clearly separates it from the sibling list_runs, which has no such filter, and names the domain concept (HITL queue) an agent can key on.

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?

Gives the selection condition (paused awaiting human approval/input) and an explicit exclusion ('a request whose session has already moved on is not listed... answering it would resume a superseded turn'). It does not explicitly name the complementary sibling answer_pending_input at the point of use, but the context is unambiguous.

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