Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Sharelist Detail

sharelist_detail
Read-onlyIdempotent

Retrieve the full details of a community sharelist by its unique ID. Specify the sharelist ID to access its composition and metadata.

Instructions

Get community sharelist detail by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSharelist ID
_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.

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: -{
-  "$defs": {
-    "SharelistConstituent": {
-      "properties": {
-        "change_rate": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "last_done": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "constituents": {
-      "items": {
-        "$ref": "#/$defs/SharelistConstituent"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "description": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.8.7
    • addedOutput schema / properties / description
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SharelistIdParam"
  5. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / SharelistConstituent / description
      Removed value: -"A single constituent of a sharelist detail. Subset of upstream fields;\nquote fields are stringified by the transform pipeline."
    • removedOutput schema / $defs / SharelistConstituent / properties / change_rate / description
      Removed value: -"Change rate (stringified decimal / percentage)."
    • removedOutput schema / $defs / SharelistConstituent / properties / last_done / description
      Removed value: -"Latest traded price (stringified decimal)."
    • removedOutput schema / $defs / SharelistConstituent / properties / name / description
      Removed value: -"Display name of the security."
    • removedOutput schema / $defs / SharelistConstituent / properties / symbol / description
      Removed value: -"Security symbol, e.g. \"AAPL.US\"."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `sharelist_detail`. Subset of the upstream detail payload: list\nmetadata plus the constituent rows. Additional quote and subscription\nfields may be present but are not enumerated here."
    • removedOutput schema / properties / constituents / description
      Removed value: -"Constituent securities with quote snapshots."
    • removedOutput schema / properties / description
      Removed value: -{
-  "description": "List description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / id / description
      Removed value: -"Sharelist ID."
    • removedOutput schema / properties / name / description
      Removed value: -"List name."
    • removedOutput schema / title
      Removed value: -"SharelistDetailResponse"
  6. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "SharelistConstituent": {
+      "description": "A single constituent of a sharelist detail. Subset of upstream fields;\nquote fields are stringified by the transform pipeline.",
+      "properties": {
+        "change_rate": {
+          "description": "Change rate (stringified decimal / percentage).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "last_done": {
+          "description": "Latest traded price (stringified decimal).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name of the security.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol, e.g. \"AAPL.US\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `sharelist_detail`. Subset of the upstream detail payload: list\nmetadata plus the constituent rows. Additional quote and subscription\nfields may be present but are not enumerated here.",
+  "properties": {
+    "constituents": {
+      "description": "Constituent securities with quote snapshots.",
+      "items": {
+        "$ref": "#/$defs/SharelistConstituent"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "List description.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Sharelist ID.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "List name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "SharelistDetailResponse",
+  "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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds only the scoping detail that this is a 'community' sharelist and a detail fetch, which is minimal behavioral context. No contradiction with annotations.

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?

A single seven-word sentence that contains only meaningful information: the operation, the resource, and the lookup key. No fluff, front-loaded, and easily parsed.

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 get-by-id tool with rich annotations, the description is minimally viable but does not describe the response shape or content of the 'detail' (e.g., whether it includes list items, metadata, permissions). With no output schema, a bit more context about what the response contains would improve completeness.

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 both id and _jq are already documented. The description's 'by id' merely restates the schema's required parameter without adding new semantics. Baseline 3 is appropriate.

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 uses a specific verb ('Get') and resource ('community sharelist detail') and identifies the lookup key ('by id'). It clearly distinguishes from sharelist_list/sharelist_popular (which presumably return collections) without explicitly naming them. Slightly below 5 because it doesn't name the alternative tools.

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?

No guidance is provided about when to use this tool versus alternatives like sharelist_list or sharelist_popular. The 'by id' qualifier implies a single-item lookup, but there is no explicit when-to-use or when-not-to-use context.

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