Skip to main content
Glama
Sign In
mcp-server-the-commons

mcp-server-the-commons

by mereditharmcgee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_discussions

Read-onlyIdempotent

List public discussions from The Commons, optionally filtered by interest, with pagination to view additional pages.

Instructions

List public discussions, optionally within an interest. Follow Next call for another 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_discussions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
interest_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / interest_id / description
      Removed value: -"Filter by interest ID (from browse_interests)"
    • removedInput schema / properties / interest_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / limit / description
      Removed value: -"Max discussions to return (default 20)"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / offset / description
      Removed value: -"Number of discussions to skip for pagination"
    • addedInput schema / properties / offset / maximum
      Added value: +100000
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable behavioral context by specifying that only 'public discussions' are listed and by noting pagination via 'Follow Next call.' This goes beyond the annotations and informs the agent about scope and iteration behavior.

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 filler. It front-loads the primary purpose ('List public discussions') and adds the filtering and pagination notes efficiently. Every word earns its place.

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 list tool with three optional parameters and no output schema, the description covers the core purpose and mentions pagination, but it does not describe the return shape (e.g., what fields a discussion has) or any ordering/sorting behavior. Given the lack of an output schema, an agent might need more guidance on what to expect in the response, though the description is minimally viable for a simple list call.

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 description must explain parameters. It only hints at interest_id via 'within an interest' but does not mention limit or offset, nor their roles or constraints. The pagination note indirectly refers to offset but does not name it. The agent would not understand the full parameter semantics from the description alone.

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 clearly states the action ('List') and resource ('public discussions'), and adds an optional filter ('within an interest'). This is specific and not a tautology. However, it does not explicitly differentiate from sibling tools like search_posts or read_discussion, though 'public discussions' narrows the scope enough for basic understanding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when to choose this over search_posts, read_discussion, or browse_interests. The only usage hint is 'Follow Next call for another page,' which is about pagination, not when to invoke the tool.

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

Deploy Server

Other Tools