Skip to main content
Glama
loomiomcp
by soil-dev

list_threads

Read-onlyIdempotent

Lists visible threads newest first with IDs, titles, groups, counters, and URLs, excluding message bodies. Filter by group or type and page results, using a since cutoff to find recent activity.

Instructions

The cheapest 'what is new across everything I can see': 1 call lists every visible thread, newest activity first (topic_id, type, title, group_id, counters, url; no bodies). group_id / type filter client-side within the page (one group: list_discussions / list_polls). No date filter upstream: pass since and page with scope.next_offset until scope.exhausted.

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

Input Schema

NameRequiredDescriptionDefault
typeNoKeep only Discussion or Poll threads (client-side).
limitNoThreads per page, default 20, max 100.
sinceNoISO-8601 cutoff on last_activity_at; page until scope.exhausted.
offsetNoThreads to skip. Default 0.
group_idNoOnly this group's threads (client-side; `total` stays instance-wide).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • addedInput schema / properties / since / maxLength
      Added value: +64
  2. Addedv0.0.13

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, but the description adds substantive behavior the annotations do not: return fields ('topic_id`, `type`, `title`, `group_id`, counters, `url`; no bodies'), ordering ('newest activity first'), and the fact that filtering happens client-side within a page. It also discloses pagination termination semantics via `scope.next_offset` / `scope.exhausted`.

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?

The description is dense but front-loaded, leading with the core value proposition and then giving the exception, return shape and paging loop in three compact sentences. Every clause carries operational information; nothing is redundant or padding.

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

Completeness5/5

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

For a read-only list tool with no output schema, the definition supplies the return fields, ordering, filtering caveats and the pagination loop an agent needs to call it correctly. No critical caller-facing behavior is left undisclosed.

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?

Schema description coverage is 100%, so the baseline is 3; the description still adds meaning by stating that `group_id` and `type` filter client-side within the page and that `since` has no upstream date filter, requiring paging with `scope.next_offset`. It does not add details for `limit` or `offset` beyond the schema, so it is not fully additive.

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?

The description states a specific verb and resource ('1 call lists every visible thread, newest activity first') and defines scope as 'everything I can see'. It explicitly distinguishes itself from single-group siblings ('one group: list_discussions / list_polls'), so an agent can route between them without opening schemas.

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?

It names the exact alternatives for a narrower use case ('one group: list_discussions / list_polls') and gives the paging procedure when a date cutoff is needed ('pass `since` and page with `scope.next_offset` until `scope.exhausted`'). It also flags the absence of an upstream date filter, which is the key usage constraint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.