Skip to main content
Glama

list_pending

Read-onlyIdempotent

Lists an agent's pending human-input requests—questions, approvals, and browser takeovers—so you can see what needs attention; only questions can be answered through this connector.

Instructions

Read the agent's requests that wait for a person: questions, approvals, and browser takeovers. Only questions can be answered through this connector; approvals stay in OpenBot.

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": {
      "agent": "<agent>"
    },
    "name": "list_pending"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent ID or exact name from list_agents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds context the annotations cannot: the returned set is mixed, and only the question subset is actionable via this connector while approvals must be handled elsewhere. It does not cover ordering, pagination, or empty-result behavior.

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 sentences, front-loaded with what the tool returns, followed by the actionable/not-actionable split. No redundant restatement of the title or annotations.

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?

For a single-parameter read tool with full annotation coverage, the definition covers what it returns and what part is actionable. With no output schema, a brief note on the shape of each pending item or result ordering would close the last gap.

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 100%, so the single 'agent' parameter (ID or exact name from list_agents) is already fully documented in the schema. The description adds no further detail about scoping or what happens with an unknown agent; baseline 3 applies when the schema carries the parameter meaning.

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 (read) and resource (the agent's pending requests for a human), then enumerates the three item kinds: questions, approvals, browser takeovers. An agent immediately knows what comes back without opening the schema.

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?

The clause 'Only questions can be answered through this connector; approvals stay in OpenBot' tells the agent when this tool's output is actionable and when it is not, which is a real usage boundary. It stops short of naming the concrete follow-up tool (e.g. answer_prompt), so routing is implied rather than spelled out.

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