Skip to main content
Glama

list_workflow_approvals

Read-only

AI-drafted workflow messages waiting for the coach's approval (drafts expire after 3 days). Show the draft and client to the coach; use review_workflow_draft to send or discard.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is to add context beyond that, and it does: it discloses a 3-day expiry on drafts and states the intended presentation ('show the draft and client to the coach'). It does not describe ordering, counts, or empty-state behavior, which would round it out.

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 short sentences, front-loaded with what the queue contains, followed by the action handoff. Every clause carries information: scope, expiry, presentation, and next tool. No filler or restatement of the name.

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 zero parameters and no output schema, an agent needs only to know what this returns conceptually and what to do next, both of which are covered (drafts plus their clients, then review_workflow_draft). Minor gaps remain around what identifying fields accompany each draft, which matters for a queue the coach must act on.

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 no parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing filtering options and instead spends its words on the queue's meaning and the follow-up action.

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?

Names a specific verb+resource ('list_workflow_approvals' = AI-drafted workflow messages awaiting coach approval) and immediately scopes it to a queue of pending items rather than all drafts. The parenthetical expiry note further distinguishes this queue from a general draft listing.

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?

Explicitly routes the agent: use this tool to surface the draft and client to the coach, then use review_workflow_draft to send or discard. That is clear when-to-use plus a named alternative. It stops short of an explicit 'do not use this to send/discard' exclusion, but the handoff makes the boundary unambiguous.

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.