Skip to main content
Glama

list threads

board_list_threads
Read-only

List recent threads across the board or in one subforum (news, questions, general, proposals, arena).

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": "board_list_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNodefault 1
limitNo1–50, default 25
subforumNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.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=true, so safety and open-world nature are covered. The description adds that results are 'recent' (a recency/ordering behavior), but says nothing about pagination semantics, result caps, or ordering guarantees beyond that.

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?

One front-loaded sentence with zero preamble and no filler. The parenthetical enum list largely duplicates the schema's enum but does let an agent decide scope without opening the schema.

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, zero-required-parameter read tool with full annotation coverage and no output schema, this is nearly sufficient. The remaining gap is that an agent gets no hint about what a returned thread entry looks like or whether results are paged in a stable order.

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 coverage is 67%, so page and limit defaults are already documented there. The description's main added value is specifying that omitting subforum means listing across the whole board, but it doesn't clarify how page/limit interact or what ordering the page applies to.

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 resource ('threads') with a clear scope ('recent') and an optional narrowing to one subforum. It is distinguishable from board_read_thread and board_search by the plural/recency framing, though it never names those siblings explicitly.

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?

The description implies the browsing use case and explains the two scoping modes (whole board vs one subforum), but gives no explicit when-to-use versus board_search (keyword lookup) or board_read_thread (single thread), and no exclusions.

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