Skip to main content
Glama
agentisend

agentisend

List my held actions and their decisions

list_agent_actions
Read-onlyIdempotent

Retrieve held actions in pending, approved, rejected, or killed states to see each decision, decision time, reason, and payload shape; filter by state or list all.

Instructions

Purpose: read your held actions in any state — pending, approved, rejected, killed — and find out what a person decided and why. NOT for: reading what a held message said; tools see shapes, not contents. Returns: each action with its state, decision time, the reason given, and a shape of its payload. Filter by state, or omit it for everything. list_pending_approvals is this list narrowed to what is still waiting.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-100).
stateNoOnly actions in this state. Omit for all of them.
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 readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful non-obvious behavior: tools see payload 'shapes, not contents', and it enumerates the returned fields (state, decision time, reason, payload shape). It does not mention pagination behavior beyond the cursor parameter, which keeps it from a 5.

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?

Four front-loaded labeled sentences (Purpose / NOT for / Returns / filter routing), each carrying distinct information with no repetition of structured fields. Nothing wasted.

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 annotations covering the safety profile, a 100% covered schema, and an output schema present, the description supplies exactly the missing pieces: scope versus the sibling, the shape-not-content limitation, and return-field summary. Nothing an agent needs to select or invoke it is absent.

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 schema already documents limit, state, and cursor. The description reinforces the state filter and the omit-for-all semantics but adds no format or edge-case detail beyond what the schema provides — baseline 3.

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 ('read your held actions') and enumerates the states covered (pending, approved, rejected, killed), plus what is retrieved (what a person decided and why). It explicitly distinguishes itself from the sibling list_pending_approvals as 'this list narrowed to what is still waiting.'

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?

Gives explicit when ('find out what a person decided and why'), an explicit when-not ('NOT for: reading what a held message said'), and names the alternative sibling (list_pending_approvals) with the condition that selects it. Filtering guidance ('filter by state, or omit it for everything') is also stated.

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