Skip to main content
Glama

List pages to approve

list_pages_to_approve
Read-only

The wiki pages waiting on YOUR approval — what to answer when your person asks «what is waiting for my signature». A page is listed when its lead named you with ask_wiki_page_approval and no approval of yours stands on the edition you were asked about or a later one: approving takes it off, being asked again about a newer edition puts it back. A page read as signatures ('mode': 'signatures') is listed while your signature does not stand on the edition it is at NOW — an edit after you signed puts it back by itself. Each row: 'pageId', 'title', 'spaceKey', 'projectKey' and 'projectName', 'askedBy' (display name) and 'askedByUsername', 'askedAt', 'askedFor' (the edition you were asked about), 'version' (the edition the page is at now — read that one before approve_wiki_page, which takes the version you read) and 'note'. Newest ask first; only pages you can open now. Questions put to you on issues are list_issue_questions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description nonetheless adds real behavioral context beyond them: the inclusion/exclusion lifecycle (approving removes the page, a newer ask or later edit re-adds it), signature-mode pages, ordering ('Newest ask first') and a visibility restriction ('only pages you can open now'). That is useful, though return format specifics stay implicit.

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?

One dense paragraph, front-loaded with the core statement before the eligibility rules. Some clause repetition around 'puts it back', but each sentence contributes a distinct rule an agent needs, and there is no filler.

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 no parameters and no output schema, the description carries the full burden and does so by enumerating every returned field ('pageId', 'title', 'spaceKey', 'projectKey'/'projectName', 'askedBy', 'askedAt', 'askedFor', 'version', 'note') plus ordering. Field types and the exact 'mode' values remain slightly underspecified, but nothing essential for correct invocation is missing.

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 the baseline is 4 and there is nothing schema-side to compensate for. The description instead spends its space documenting the output row fields, which is value-add even if not strictly parameter semantics.

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+resource ('The wiki pages waiting on YOUR approval') and immediately frames the practical question it answers. It is clearly distinguishable from approve_wiki_page and list_issue_questions, which are both named in the text.

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?

Gives an explicit usage trigger ('when your person asks «what is waiting for my signature»') and routes the adjacent case elsewhere ('Questions put to you on issues are list_issue_questions'). It also warns that the listed 'version' is what approve_wiki_page should be called with, which is genuine when-to-use guidance.

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