Skip to main content
Glama

The world according to capital

List the curation queue

list_pending_bookmarks
Read-only

List pending bookmarks for curation, newest first. Curator only.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two genuine facts beyond that: results are sorted newest first and the endpoint is restricted to curators. It stops short of describing response shape or what happens past the last page.

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?

Two short sentences with the core scope front-loaded and no filler. The access restriction trails as a second sentence, which is a reasonable placement, though it could be merged for tighter reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with annotations covering the safety profile, the description covers purpose, ordering, and access control. It leaves gaps on pagination behavior and, since there is no output schema, on what a returned bookmark entry contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema alone gives only types and defaults for page and limit; the description says nothing about paging behavior, page size limits, or how results are paginated. It neither compensates for the coverage gap nor explains whether omitting parameters returns the full queue.

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?

States a specific verb ('List') and a scoped resource ('pending bookmarks for curation'), plus an ordering guarantee ('newest first'), which distinguishes it from the unfiltered sibling list_bookmarks. It does not name the sibling explicitly, so differentiation is implied by 'pending' rather than stated outright.

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?

'for curation' and 'Curator only' imply the workflow context and the caller's required role, but there is no explicit statement of when to use this rather than list_bookmarks or when to move on to approve_bookmarks/reject_bookmarks. Usage is inferable but not spelled out.

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