Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Delete Watchlist Group

delete_watchlist_group
DestructiveIdempotent

Delete a watchlist group by its numeric ID, with an option to purge its securities from all other groups.

Instructions

Delete a watchlist group by id (numeric). Set purge=true to also remove its securities from all other groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWatchlist group 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.
purgeYesWhether to also remove the securities from other groups

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 / id / format
      Removed value: -"int64"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "deleted": {
-      "type": "boolean"
-    },
-    "id": {
-      "format": "int64",
-      "type": "integer"
-    }
-  },
-  "required": [
-    "id",
-    "deleted"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"DeleteWatchlistGroupParam"
  4. Changed5 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 `delete_watchlist_group`."
    • removedOutput schema / properties / deleted / description
      Removed value: -"Always `true` on success."
    • removedOutput schema / properties / id / description
      Removed value: -"The deleted watchlist group ID (echoed from the request)."
    • removedOutput schema / title
      Removed value: -"DeleteWatchlistGroupResponse"
  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 `delete_watchlist_group`.",
+  "properties": {
+    "deleted": {
+      "description": "Always `true` on success.",
+      "type": "boolean"
+    },
+    "id": {
+      "description": "The deleted watchlist group ID (echoed from the request).",
+      "format": "int64",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "deleted"
+  ],
+  "title": "DeleteWatchlistGroupResponse",
+  "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.2/5.0
Behavior4/5

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

Annotations already signal destructiveHint and idempotentHint, so the description doesn't need to restate those. It adds valuable behavioral context by explaining the purge side effect: securities are removed from all other groups. It does not mention irreversibility or permissions, but the destructive annotation covers the main warning.

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?

Two short, front-loaded sentences. The primary action and required parameter come first, followed by the optional behavior. Every word earns its place.

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 simple delete operation, the description combined with schema and annotations covers what an agent needs: the action, the required id, and the purge behavior. No output schema exists, so return-value details are less critical. It could be slightly more explicit about the purge=false postcondition or alternatives, but it is complete for effective invocation.

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 explains id, purge, and _jq. The description adds only marginal restatement ('numeric', 'remove its securities from all other groups'), which is helpful but not a substantial semantic expansion beyond the schema.

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 names the exact operation ('Delete a watchlist group'), specifies the identifier ('by id (numeric)'), and defines the conditional scope ('Set purge=true to also remove its securities from all other groups'). It is clearly distinct from sibling tools like create_watchlist_group and update_watchlist_group.

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 gives a clear context: use this when deleting a watchlist group by numeric id, and sets out the purge variant. It does not explicitly contrast with create/update alternatives, but the delete intent is unambiguous enough that an agent can select it correctly.

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