Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Popular Sharelists

sharelist_popular
Read-onlyIdempotent

Retrieve trending community lists to see popular stock picks and investment ideas. Set count to adjust number of lists returned.

Instructions

Get popular/trending community sharelists.

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.
countNoNumber of lists to return (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • removedInput schema / properties / count / format
      Removed value: -"uint32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "SharelistSummary": {
-      "properties": {
-        "creator": {},
-        "description": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "follower_count": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "is_owner": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol_count": {
-          "format": "int64",
-          "type": [
-            "integer",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "lists": {
-      "items": {
-        "$ref": "#/$defs/SharelistSummary"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.8.7
    • addedOutput schema / $defs / SharelistSummary / properties / description
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SharelistCountParam"
  5. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / SharelistSummary / description
      Removed value: -"A single sharelist summary entry. Subset of upstream fields."
    • removedOutput schema / $defs / SharelistSummary / properties / creator / description
      Removed value: -"Creator info (`sharelist_popular` only); passthrough, shape\nupstream-defined."
    • removedOutput schema / $defs / SharelistSummary / properties / description
      Removed value: -{
-  "description": "List description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / $defs / SharelistSummary / properties / follower_count / description
      Removed value: -"Number of followers / subscribers of this list."
    • removedOutput schema / $defs / SharelistSummary / properties / id / description
      Removed value: -"Sharelist ID."
    • removedOutput schema / $defs / SharelistSummary / properties / is_owner / description
      Removed value: -"Whether the current user owns this list (`sharelist_list` only)."
    • removedOutput schema / $defs / SharelistSummary / properties / name / description
      Removed value: -"List name."
    • removedOutput schema / $defs / SharelistSummary / properties / symbol_count / description
      Removed value: -"Number of securities in the list."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `sharelist_list` and `sharelist_popular`. Documented portion is\n`lists[]`."
    • removedOutput schema / properties / lists / description
      Removed value: -"Sharelist summaries."
    • removedOutput schema / title
      Removed value: -"SharelistListResponse"
  6. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "SharelistSummary": {
+      "description": "A single sharelist summary entry. Subset of upstream fields.",
+      "properties": {
+        "creator": {
+          "description": "Creator info (`sharelist_popular` only); passthrough, shape\nupstream-defined."
+        },
+        "description": {
+          "description": "List description.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "follower_count": {
+          "description": "Number of followers / subscribers of this list.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Sharelist ID.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "is_owner": {
+          "description": "Whether the current user owns this list (`sharelist_list` only).",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "List name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol_count": {
+          "description": "Number of securities in the list.",
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `sharelist_list` and `sharelist_popular`. Documented portion is\n`lists[]`.",
+  "properties": {
+    "lists": {
+      "description": "Sharelist summaries.",
+      "items": {
+        "$ref": "#/$defs/SharelistSummary"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "SharelistListResponse",
+  "type": "object"
+}
  7. Addedv0.4.5
  8. Removedv0.4.0
  9. Addedv0.3.2
  10. Removedv0.3.1
  11. First observedv0.1.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds the 'popular/trending community' scope but does not disclose output shape, pagination, or limits, which matters since no output schema exists. No contradiction with annotations is present.

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 description is a single, efficient sentence with no filler. It front-loads the action and resource immediately, matching the tool name and title without redundancy.

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 simple read-only tool with 0 required parameters, the description is minimally adequate. However, it would be more complete if it mentioned the expected response type or pointed to sharelist_list for personal lists; the absence of an output schema leaves some behavioral ambiguity.

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%: both _jq and count are documented in the schema, including the default count of 20. The description adds no extra meaning beyond the schema, so it stays at the baseline for high coverage.

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 names a specific verb and resource: 'Get popular/trending community sharelists.' It clearly distinguishes this from user-owned sharelists via the 'community' qualifier, even though it does not explicitly name sibling tools like sharelist_list or sharelist_detail.

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 gives no when-to-use guidance or alternatives. It does not state that this is for community/trending lists while sharelist_list is for the user's own lists, so an agent must infer the intended context from the tool name and title alone.

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