Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Create Topic

topic_create

Create a discussion topic on Longbridge: publish a plain-text post or a Markdown article with an optional title and related security symbols.

Instructions

Create a new discussion topic. topic_type="post" (default) is plain text; "article" requires a non-empty title and accepts Markdown body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
bodyYesTopic body. "post" type is plain text only; "article" type accepts Markdown.
titleYesTopic title. Required when topic_type is "article", optional for "post".
symbolsNoRelated security symbols, e.g. ["700.HK", "TSLA.US"] (max 10).
topic_typeNoTopic type: "post" (default, plain text) or "article" (Markdown, title required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "id": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "id"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"TopicCreateParam"
  4. Changed4 schema fields changedv0.6.0
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `topic_create`. The handler wraps the new topic ID in a single\n`{ \"id\": ... }` object."
    • removedOutput schema / properties / id / description
      Removed value: -"ID of the newly-created topic. Pass to `topic_detail` / `topic_replies`."
    • removedOutput schema / title
      Removed value: -"TopicCreateResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `topic_create`. The handler wraps the new topic ID in a single\n`{ \"id\": ... }` object.",
+  "properties": {
+    "id": {
+      "description": "ID of the newly-created topic. Pass to `topic_detail` / `topic_replies`.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "title": "TopicCreateResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate it's a non-read-only mutation (readOnlyHint=false, idempotentHint=false), so the description doesn't need to restate that. It does add useful behavioral context: it clarifies that 'article' requires a title and accepts Markdown, while 'post' is plain text. However, it doesn't describe side effects or response behavior, but with annotations covering the mutation profile, this is adequate.

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 sentences with no filler. The primary action is front-loaded, and the essential type distinction is conveyed efficiently. Every word earns its place; there is no superfluous information.

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 create operation with 5 parameters (2 required) and no output schema, the description covers the core purpose and the critical type-specific requirements. It doesn't explain the symbols or _jq parameters, but those are fully described in the schema. The description is complete enough for an agent to understand what the tool does and when to use it, without needing additional context.

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 the schema already documents all parameters. The description adds a concise summary of the relationship between topic_type, title, and body, but this largely repeats what the schema states (e.g., title required for article, body format). It doesn't add significantly new semantics beyond the schema, so a baseline score of 3 is appropriate.

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?

The description clearly states the action ('Create a new discussion topic') and identifies the resource (a discussion topic). It further differentiates between two topic types, 'post' and 'article', which is essential for correct invocation and distinguishes this tool from topic_create_reply and other topic-related siblings. This is a specific, unambiguous purpose.

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?

The description provides clear guidance on when to use each topic type: 'post' for plain text and 'article' for Markdown with a required title. It does not explicitly compare to sibling tools, but the verb 'create' and the distinction from 'topic_create_reply' are evident from the name. The context is sufficient for an agent to decide between topic types, though it doesn't state when not to use this tool in favor of alternatives.

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