Skip to main content
Glama
Sign In

Prubex

by com.prubex
OverviewDiscussionsAdmin

List approval requests

approvals_list
Read-onlyIdempotent

Lists the sends, invitations, answers and Prubex suggestions you asked for that were held for a person to approve, newest first. Filter by status (pending, approved, executed, rejected, expired, cancelled, failed), and by account_id or profile_id (the accounts a profile holds now; account_id wins if you pass both). Suggestions concern no account, so an account_id or profile_id filter leaves them out. Use it to tell the user what is still waiting and what happened to the rest; read one in full with approvals_get. Example: { "status": "pending" }.

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": "approvals_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, 1–100 (default 20).
cursorNoThe `next_cursor` from the previous page. Omit for the first page.
statusNoOnly approvals in this state.
account_idNoOnly approvals for this account (`acc_…`).
profile_idNoOnly approvals for accounts now in this profile (`prf_…` from profiles_list).

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorNoPass as `cursor` for the next page; absent on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description adds useful semantics: results are newest first, account_id wins when both filters are passed, and suggestion approvals are excluded by account/profile filters. It does not discuss pagination behavior, but the schema already documents limit and cursor.

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?

The description is front-loaded with purpose and ordering, then filters and usage guidance. It is appropriately sized, though the status enum repeats schema information and the sentences are somewhat dense.

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?

For a list tool with an output schema, full schema description coverage, and rich read-only annotations, the description covers purpose, filtering semantics, ordering, alternative usage, and a concrete example. Nothing critical is missing for correct invocation.

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 meaningful filter semantics beyond the schema descriptions: account_id takes precedence over profile_id, profile_id means accounts now in the profile, and suggestion records have no account and are excluded by those filters. It does not add anything for limit/cursor, but those are fully schema-documented.

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 states a specific verb and resource ('Lists ... held for a person to approve') with clear scope and ordering ('newest first'). It explicitly distinguishes itself from approvals_get, letting an agent understand it as the list counterpart to the single-item getter.

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?

It explicitly says when to use it ('tell the user what is still waiting and what happened to the rest') and names the alternative for reading one in full ('approvals_get'). It also explains filter behavior and edge cases, leaving little inference needed.

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

All Prubex toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources