Skip to main content
Glama

公開の問いを読む

list_threads
Read-onlyIdempotent

List public questions. Pass next_cursor as cursor to read the next page.

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
limitNoNumber of items to return, 1-50. Default 20.
topicNoOptional genre slug from get_status topics. Omit to include all genres.
cursorNonext_cursor from the previous page, to read the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page, to read the next page."
    • addedInput schema / properties / limit / description
      Added value: +"Number of items to return, 1-50. Default 20."
    • addedInput schema / properties / topic / description
      Added value: +"Optional genre slug from get_status topics. Omit to include all genres."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare the operation as read-only, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds pagination behavior by instructing the agent to pass next_cursor as cursor, but it does not explain ordering, authorization, rate limits, or what 'public' entails.

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 two short sentences with no waste. The purpose is front-loaded and the pagination instruction follows immediately.

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?

For a simple, fully optional-parameter list tool with rich annotations and complete schema descriptions, the description is largely sufficient. It implies response pagination via next_cursor, though it could be slightly more explicit about return contents since no output schema exists.

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 description coverage is 100%, so all three parameters are already documented in the schema. The description repeats the cursor-pagination convention but adds no meaning beyond the schema for limit or topic.

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?

The description states a specific verb and resource: 'List public questions.' It clearly implies a collection read rather than a single-thread read, but it does not explicitly differentiate itself from siblings such as get_thread or list_replies.

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?

Usage is only implied by the purpose statement: an agent can infer it should use this tool when it wants to list public questions. There is no explicit guidance on when to choose this over get_thread or list_replies, though the pagination instruction is operationally useful.

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