Skip to main content
Glama

List pending actions

list_pending_actions
Read-onlyIdempotent

List pending actions. View is awaiting_my_approval (the default) or requested_by_me. Each item includes human_link. At most 200 are returned per page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pending_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoawaiting_my_approval (the default) or requested_by_me.
limitNoPage size, a whole number from 1 to 200. Omit it for 50.
cursorNoOpaque position returned as next_cursor by the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. Beyond that, the description adds useful behavioral context: each item includes human_link and responses are capped at 200 per page. It does not explain ordering or permission requirements, but the annotations cover the safety profile.

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?

Three short sentences, front-loaded with the action and then the key scoping and return details. Every sentence carries information an agent would otherwise have to infer.

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 simple read-only list tool with fully described parameters and rich annotations, the description covers the key operational facts: available views, default view, item field, and page cap. It does not discuss ordering or empty-result behavior, but the cursor parameter schema supplies pagination mechanics.

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 description coverage is 100%, so the input schema already documents the view enum, limit range/default, and cursor semantics. The description restates the view values and page cap but adds no syntax, format, or edge-case detail beyond the schema.

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?

The description opens with a specific verb and resource, 'List pending actions', and immediately scopes it by view. An agent can distinguish this listing operation from sibling tools like get_pending_action and cancel_pending_action by name alone.

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?

The description explains the two views and identifies awaiting_my_approval as the default, which gives implied usage guidance. However, it does not state when to use this tool rather than get_pending_action or cancel_pending_action, nor does it provide exclusions or prerequisites.

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.

Resources