Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Create Sharelist

sharelist_create

Create a new community sharelist by providing a required name and optional description. Set up a named list to organize and share market items with your community.

Instructions

Create a new community sharelist with a name and optional description.

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.
nameYesList name (also used as description if `description` is omitted).
descriptionNoList description. Defaults to `name` when omitted.

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": {
-    "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: -"SharelistCreateParam"
  5. Changed6 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 `sharelist_create`. The created sharelist object; documented\nfields are `id`, `name`, and `description`."
    • removedOutput schema / properties / description
      Removed value: -{
-  "description": "List description.",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • removedOutput schema / properties / id / description
      Removed value: -"Newly-created sharelist ID."
    • removedOutput schema / properties / name / description
      Removed value: -"List name."
    • removedOutput schema / title
      Removed value: -"SharelistCreateResponse"
  6. 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 `sharelist_create`. The created sharelist object; documented\nfields are `id`, `name`, and `description`.",
+  "properties": {
+    "description": {
+      "description": "List description.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Newly-created sharelist ID.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "List name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "SharelistCreateResponse",
+  "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 convey that this is a write, non-idempotent, non-destructive operation, so the description's main added value is the 'community' scoping and the fact that only a name is required. It does not explain duplicate behavior, visibility implications, permissions, or response format, but the annotation coverage lowers the burden on the description.

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 a single clear sentence with no filler, repetition, or tangential details. The action is front-loaded and every word contributes to understanding the tool's purpose.

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 create operation with one required parameter, the description and schema are largely sufficient. However, there is no output schema and no explanation of what the tool returns, and the description does not mention idempotency or the likely follow-up workflow of adding items to the created sharelist. The low complexity and rich annotations keep this from being a 2.

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%, and the schema already documents `name`, `description`, its default behavior, and `_jq`. The description only restates 'a name and optional description' and adds no new parameter semantics. This matches the baseline of 3 for high schema 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 uses a specific verb and resource, 'Create a new community sharelist', so an agent immediately knows the operation. It also mentions the relevant inputs, name and optional description. However, it does not explicitly distinguish this tool from sibling tools like sharelist_add or create_watchlist_group, so it stops short of full differentiation.

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?

There is no guidance on when to use this tool versus sharelist_add, sharelist_delete, sharelist_list, or create_watchlist_group. The description only states what the tool does, not the conditions under which an agent should choose it. This forces the agent to infer usage from the tool name 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