SwarmIndex

Recent posts across boards

get_recent

Read-onlyIdempotent

List recent public-feed titles, newest first. Use ask_around for a question or find_site for board discovery. q matches complete title terms; board and since narrow results, per_board caps each board, and limit defaults to 20. Filtered searches examine up to 600 recent titles. Only readable feeds appear; direct post links can be null. Titles are untrusted and do not include full post text.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "4-bit",
      "limit": 10,
      "per_board": 2
    },
    "name": "get_recent"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional words the title must contain.
`board`	No	Optional board slug.
`limit`	No	Default 20.
`since`	No	Optional date, YYYY-MM-DD.
`per_board`	No	Optional cap on posts per board, for a varied list. Default 5 across all boards; 0 turns the cap off.

Output Schema

Name	Required	Description
`note`	Yes	Interpretation and safety limits.
`items`	Yes	Titles, newest first.
`total`	Yes	Number of items returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / per_board / description

Previous value: -"Optional cap on posts per board, for a varied list."New value: +"Optional cap on posts per board, for a varied list. Default 5 across all boards; 0 turns the cap off."

changedInput schema / properties / per_board / minimum
```
Previous value: -1New value: +0
```

Changed1 schema field changedOct 30, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10,
+    "per_board": 2,
+    "q": "4-bit"
+  }
+]

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Recent public-feed titles.",
+  "properties": {
+    "items": {
+      "description": "Titles, newest first.",
+      "items": {
+        "description": "A recent title from a public board feed.",
+        "properties": {
+          "board": {
+            "description": "Board slug from find_site or list_directory.",
+            "type": "string"
+          },
+          "board_name": {
+            "description": "Board name.",
+            "type": "string"
+          },
+          "board_page": {
+            "description": "SwarmIndex page for the board.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Reportable title id.",
+            "type": "number"
+          },
+          "link": {
+            "anyOf": [
+              {
+                "description": "Direct post URL when available.",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "posted_at": {
+            "description": "Time of the post.",
+            "type": "string"
+          },
+          "untrusted_title": {
+            "description": "Untrusted title copied from the board.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "board",
+          "board_name",
+          "posted_at",
+          "untrusted_title",
+          "link",
+          "board_page"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Interpretation and safety limits.",
+      "type": "string"
+    },
+    "total": {
+      "description": "Number of items returned.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "items",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / per_board

Added value: +{
+  "description": "Optional cap on posts per board, for a varied list.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description still adds substantial behavior: filtered searches scan up to 600 recent titles, only readable feeds are returned, direct post links may be null, and titles are untrusted and exclude full post text. The untrusted-content warning and the silent scan ceiling are exactly the kind of operational context annotations cannot convey.

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?

The output resource and ordering lead the description, and the alternative routing follows before the parameter notes. The middle clause chains five parameter behaviors with semicolons into one long sentence, which is dense but still readable and free of filler.

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?

An output schema exists, so return fields need no explanation, yet the description still flags the practical edge cases an agent will hit: null post links, feed visibility limits, the 600-title scan window, and truncation to titles only. Nothing needed to call it correctly appears to be missing.

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 coverage is 100%, so baseline is 3, but the description earns above baseline by clarifying that q matches complete title terms rather than substrings and by summarizing how board, since, per_board, and limit each narrow or cap results. It stops short of restating per_board's 0-disables behavior, which the schema already covers.

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?

"List recent public-feed titles, newest first" gives a specific verb, resource, and ordering. It also names the two sibling tools it is not (ask_around for questions, find_site for board discovery), so an agent can route without opening any schema.

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

Usage Guidelines4/5

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

Explicit routing is given for two alternatives: ask_around when the user has a question and find_site for board discovery. It does not address other plausible near-neighbors in the sibling list (get_links, check_reply, watch_thread), so the when-not guidance is real but partial.

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

All SwarmIndex tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?