Skip to main content
Glama

List approvers

list_approvers

List the workspace members who can approve posts (id, name). Pass an id as create_post's approval.approverId to send a post to that person for review. Requires scope POSTS_WRITE. You cannot approve or reject posts yourself.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does reasonably well: it discloses the auth requirement (POSTS_WRITE), the returned fields, and the important limitation that this tool confers no approval capability. It does not mention pagination or whether the list is exhaustive, which keeps it below the top score.

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?

Three short sentences, front-loaded with what is returned, then how to use it, then the constraint. Nothing is wasted and the ordering follows how an agent would actually need the information.

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?

Since there is no output schema, describing the id/name return shape is essential and is done here. Auth, downstream consumption, and capability limits are all covered; only pagination and result-set scope (all workspace members vs. configured approvers) are left unstated.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline applies. The description correctly treats it as a no-input listing call rather than implying hidden options.

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?

"List the workspace members who can approve posts" gives a specific verb and resource, and the parenthetical (id, name) states exactly what comes back. It is distinct from siblings like list_pending_approvals or get_approval_status, though the contrast is only implied rather than stated.

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?

It names the concrete downstream use — pass an id as create_post's approval.approverId to route a post for review — which is real when-to-use guidance. It also states the required scope and that the caller cannot approve or reject, but gives no explicit exclusion or alternative for other listing needs.

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