Skip to main content
Glama

List pending approvals

list_pending_approvals

Read-only. Posts still waiting for a human decision (id, status, scheduledAt, approval). The agent cannot decide approval.

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.
offsetNoNumber of posts to skip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does cover the essentials: it substitutes for readOnlyHint, discloses the returned field set, and warns that the agent cannot decide approvals. It does not mention ordering, pagination behavior, or whether the pending set is scoped to the caller's account, so behavioral disclosure is partial rather than thorough.

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?

Three short sentences with the safety profile front-loaded ("Read-only.") followed by scope and the returned fields; nothing is filler. Slightly clipped phrasing (the fragment "Read-only." and the verbless "Posts still waiting...") costs a point but aids scanning.

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?

There is no output schema, so the inline field list is doing real work, and for a simple paginated read tool the description covers safety, scope, return shape, and the key limitation. Only ordering/default page-size behavior is left unstated, which is minor for this complexity.

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% and both parameters (limit, offset) are fully documented in the schema, including the 1-100 bound, so the description adds no parameter detail and none is needed. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Posts still waiting for a human decision" names a specific resource and scope, and the parenthetical enumerates what comes back (id, status, scheduledAt, approval), so an agent can tell this apart from get_approval_status or list_approvers. It lacks an explicit list verb and never states filtering/ordering, but the resource is unambiguous.

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?

"Read-only" plus "The agent cannot decide approval" implicitly tells the caller to use this for inspection and that no approval action is possible here, which is a useful exclusion. However, no sibling is named and there is no explicit statement of when to prefer this over get_approval_status; guidance must be inferred.

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