Skip to main content
Glama
agentisend

agentisend

List pending approvals

list_pending_approvals
Read-onlyIdempotent

Lists actions waiting for human approval, newest first, with IDs, types, age, and summary details so agents can identify pending work without approving or reading message contents.

Instructions

Purpose: see which of your actions are waiting on a person, newest first. NOT for: deciding one — no tool approves or rejects — or reading a held message's contents, which stay out of reach by design. Returns: each action's id, kind, age and a shape of what it holds: recipient counts, whether there is a subject, whether there is a body.

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_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-100).
cursorNonext_cursor from the previous page. Omit for the first page.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds ordering (newest first) and the deliberate opacity of held contents — meaningful context beyond the annotations — though it says nothing about pagination/cursor behavior beyond the schema.

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 labeled sentences (Purpose / NOT for / Returns) with zero filler; the differentiating 'NOT for' content is front-loaded. Every clause earns its place.

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?

With an output schema present, the description need not enumerate return fields, yet it still sketches what each entry holds. Annotations cover the safety profile and the schema covers pagination, so nothing needed to invoke this correctly is missing.

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 both limit and cursor are already documented in the schema. The description contributes only the 'newest first' ordering, which implies how cursor paging traverses results but adds no syntax or format detail. Baseline 3 is appropriate.

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 ('see which of your actions are waiting on a person') with explicit scope (newest first). The 'NOT for' clause distinguishes it from any approval-decision or message-reading tool in the sibling set, so an agent can classify it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the two nearest alternatives and rules them out: no tool approves or rejects, and held message contents are unreachable by design. This is exactly the when-not/alternative guidance the dimension asks for.

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