Skip to main content
Glama

blobpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_discussion

Read one Celestia community forum thread (forum.celestia.org) with its posts, by topic id. This is the CELESTIA FORUM channel — not GitHub Discussions (use get_github_discussion). The topic id is the number at the end of the thread link that search, get_recent_changes and the list tools print (https://blobpedia.org/discussions/2314 is topic 2314); that link is accepted as well.

Input Schema

NameRequiredDescriptionDefault
idYesForum topic number, e.g. 2314, or the thread link https://blobpedia.org/discussions/2314

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / anyOf
      Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "pattern": "^\\d{1,15}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / id / description
      Previous value: -"Forum topic ID"New value: +"Forum topic number, e.g. 2314, or the thread link https://blobpedia.org/discussions/2314"
  2. Changed4 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^\\d{1,15}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / id / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / id / type
      Removed value: -"integer"
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' plus 'thread with its posts' implies a non-destructive retrieval and hints at the payload shape, which is useful, but nothing is said about pagination of large threads, rate limits, or whether the posts are truncated — real gaps for a thread-fetching tool.

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?

Three sentences, all load-bearing: purpose first, sibling disambiguation second, identifier sourcing third. No filler and no repetition of the schema.

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 single-parameter read tool with no annotations and no output schema, the description covers what is fetched, which channel it belongs to, and how to obtain the id. It stops short of describing the returned thread/post structure or any truncation behavior, but nothing essential to calling it correctly is 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% and the schema already documents the id as an integer-or-link. The description goes further by explaining that the id is the number at the end of the thread link, that the full link is accepted, and where such links surface, which adds genuine usage meaning over the schema text.

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?

States a specific verb and resource ('Read one Celestia community forum thread with its posts') and pins down the exact channel, explicitly excluding the similarly named GitHub Discussions sibling. An agent can distinguish it from get_github_discussion, list_github_discussions, and the other get_* tools 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 Guidelines5/5

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

Names the alternative explicitly ('not GitHub Discussions — use get_github_discussion') and states the condition that selects it. It also tells the agent where the id comes from (search, get_recent_changes, the list tools), which is the practical prerequisite for invoking it.

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

All blobpedia toolsInspect
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