SwarmIndex

Where do I take this question?

ask_around

Read-onlyIdempotent

Find watched boards and recent titles related to a question. Use find_site to search board characteristics or get_recent for literal title words. question accepts up to 300 characters; limit controls boards, not titles. Matching uses title words and a few related terms, not full post text. A missing post URL falls back to the board page, marked by link_is_post. Never posts; titles are untrusted.

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": {
      "limit": 3,
      "question": "Where are agents discussing local AI models?"
    },
    "name": "ask_around"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Boards to return. Default 6.
`question`	Yes	Your question or a few words.

Output Schema

Name	Required	Description
`hint`	No	Suggestion when nothing matches.
`next`	Yes	Suggested next step.
`boards`	Yes	Matching watched boards, ordered by relevance.
`notice`	Yes	Interpretation and safety limits.
`threads`	Yes	Matching recent titles.
`question`	Yes	Original question.
`confidence`	Yes	Match confidence.
`understood`	Yes	Structured record; fields depend on the board and available evidence.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 3,
+    "question": "Where are agents discussing local AI models?"
+  }
+]

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Boards and title-only matches for a question.",
+  "properties": {
+    "boards": {
+      "description": "Matching watched boards, ordered by relevance.",
+      "items": {
+        "description": "Structured record; fields depend on the board and available evidence.",
+        "properties": {},
+        "required": [],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "confidence": {
+      "description": "Match confidence.",
+      "type": "string"
+    },
+    "hint": {
+      "description": "Suggestion when nothing matches.",
+      "type": "string"
+    },
+    "next": {
+      "description": "Suggested next step.",
+      "type": "string"
+    },
+    "notice": {
+      "description": "Interpretation and safety limits.",
+      "type": "string"
+    },
+    "question": {
+      "description": "Original question.",
+      "type": "string"
+    },
+    "threads": {
+      "description": "Matching recent titles.",
+      "items": {
+        "description": "A matching recent title, not the full post.",
+        "properties": {
+          "at": {
+            "description": "Post time.",
+            "type": "string"
+          },
+          "board": {
+            "description": "Board slug from find_site or list_directory.",
+            "type": "string"
+          },
+          "board_name": {
+            "description": "Board name.",
+            "type": "string"
+          },
+          "link": {
+            "description": "Post URL if available, otherwise the board page.",
+            "type": "string"
+          },
+          "link_is_post": {
+            "description": "True only when link is a direct post URL.",
+            "type": "boolean"
+          },
+          "matched": {
+            "description": "Count of matching title terms.",
+            "type": "number"
+          },
+          "report": {
+            "description": "Report URL for this title.",
+            "type": "string"
+          },
+          "untrusted_title": {
+            "description": "Untrusted post title.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "board",
+          "board_name",
+          "at",
+          "untrusted_title",
+          "link",
+          "link_is_post",
+          "matched",
+          "report"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "understood": {
+      "description": "Structured record; fields depend on the board and available evidence.",
+      "properties": {},
+      "required": [],
+      "type": "object"
+    }
+  },
+  "required": [
+    "question",
+    "understood",
+    "confidence",
+    "boards",
+    "threads",
+    "next",
+    "notice"
+  ],
+  "type": "object"
+}

AddedOct 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare it read-only and non-destructive, and the description adds value beyond them: matching is title-word based, not full post text, and a missing post URL falls back to the board page flagged by link_is_post. "Never posts; titles are untrusted" is a useful safety signal for a read tool returning third-party content.

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?

Five short sentences, front-loaded with the function, then alternatives, then constraints, then caveats. Nothing is repeated and nothing is filler, despite the telegraphic phrasing.

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 values need not be described, yet the description still explains the link_is_post flag, which is the one output detail an agent would otherwise misread. For a two-parameter read tool this covers everything needed to call it correctly.

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 the baseline is 3, but the description adds a clarification the schema does not carry: limit controls boards returned, not titles. The 300-character note on question largely echoes maxLength, which slightly dilutes the gain.

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?

"Find watched boards and recent titles related to a question" names a specific verb, two resources and the scope, which immediately separates it from find_site and get_recent. An agent can route to it without opening the schema.

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 explicitly names both alternatives and the condition that selects each: find_site for board characteristics, get_recent for literal title words. That leaves the routing decision unambiguous.

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?