Skip to main content
Glama

Able and Agent Sandbox

List your errands (ACTs)

list_acts
Read-onlyIdempotent

Your Principal's ACTs, newest first, each in brief, as GET /api/v1/acts: what each is, where it stands, and when its review ends; a DRAFT waits for your Principal's approval at its approvalUrl. Give state to see one state, such as SUBMITTED for work waiting on your review, and after to read on from the last id you saw. Read one whole with get_act. When you tell your Principal about it, call it an errand (ACT) the first time, and write its id as the site shows it, without act_: aTdTkM-48271.

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

Input Schema

NameRequiredDescriptionDefault
keyNoYour key, aak_…, when you cannot send it in the Authorization header. The sandbox only; on the live site the header alone is read.
afterNoThe id of the last ACT you read.
limitNoHow many to return, 1 to 100; 50 if you say nothing.
stateNoOne state's code, such as OPEN, IN_PROGRESS or SUBMITTED; omit it for every state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 real behavior: results are newest-first, items are brief rather than complete, DRAFT items expose an approvalUrl where approval is pending. It does not explain what the list's return envelope looks like or how to detect the end of pagination.

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?

Purpose is front-loaded and the paragraph is dense with information rather than filler. The trailing guidance on calling it an 'errand (ACT)' and writing ids without the act_ prefix is presentation advice that slightly dilutes the invocation-focused core, and the single long sentence makes the parameter guidance harder to scan.

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?

With no output schema and zero required parameters, the description carries the return-shape burden and does so by describing each brief item's fields and the DRAFT approvalUrl. The main remaining gap is pagination termination — it never says how to know there are no more ACTs to fetch with after.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds interpretive meaning: state is a single state code whose SUBMITTED value means work waiting on the caller's review, and after resumes from the last id already seen. The limit parameter is left entirely to the schema, which is acceptable given its explicit description of the 1-100 range and default of 50.

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 and resource ('Your Principal's ACTs, newest first') plus the underlying endpoint (GET /api/v1/acts) and what each item carries: what it is, its state, and its review end. It distinguishes itself from get_act explicitly ('Read one whole with get_act'), so an agent can separate brief-listing from single-record retrieval without opening either 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?

Gives concrete conditions for the optional filters ('Give state to see one state, such as SUBMITTED for work waiting on your review', 'after to read on from the last id you saw') and names the alternative get_act for full records. It stops short of stating exclusions or when listing is inappropriate, so it is clear context rather than a complete when/when-not rule set.

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