Skip to main content
Glama
Datris MCP Server

Datris MCP Server

list_pending_approvals

Retrieve actions an agent has queued for human approval under its policy, newest first. Filter by state (pending, approved, rejected, expired, executed, or failed) to review decisions and results.

Instructions

List the actions this agent queued for human approval under the agent policy, newest first. Each entry has id, action, resource, state (pending | approved | rejected | expired | executed | failed), createdAt, expiresAt and — once decided — decidedBy and the result. Use state to filter (default: all).

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
limitNoMaximum entries to return (default 100).
stateNoFilter by state: pending, approved, rejected, expired, executed, failed. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses result ordering (newest first), the full field set, the six possible states, and that decidedBy and result appear only after a decision is made. Gaps remain around pagination/truncation when more than `limit` entries exist and around any permission or auth requirements.

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 with zero filler. The scope and ordering constraint are front-loaded, then the return shape, then the filter hint, which matches the order an agent needs them.

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, zero-required-parameter read tool with no output schema, the description is nearly complete: it documents the return fields and state semantics in place of a missing output schema. The one shortfall is that it does not say what happens when results exceed `limit` or whether the list is truncated at the described default.

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

Parameters5/5

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

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it enumerates the state values so the filter is unambiguous, and notes that omitting state returns all entries. It also frames `limit` implicitly through the 'newest first' ordering contract, which tells the agent which entries a truncated result would contain.

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 ('List the actions this agent queued for human approval'), plus scope (agent policy) and ordering (newest first). This clearly separates it from the sibling list_* tools, which target collections, pipelines, taps, and secrets rather than approvals.

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?

Usage is only implied: an agent can infer it should call this to inspect queued or decided approval requests. The one explicit piece of guidance, 'Use `state` to filter (default: all)', is about a parameter, not about when to prefer this tool over another. No alternatives or when-not conditions are named, though the sibling list gives no obvious competing approval tool.

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

Deploy Server

Other Tools