Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Disable Price Alert

alert_disable
Idempotent

Stop unwanted price alerts by disabling a specific alert using its ID. Retrieve the numeric alert ID via alert_list, then disable it to prevent further notifications.

Instructions

Disable a price alert by alert_id. Use alert_list to find the numeric alert_id.

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.
alert_idYesAlert indicator id

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": {
-    "alert_id": {
-      "type": "string"
-    },
-    "enabled": {
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "alert_id",
-    "enabled"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"AlertIdParam"
  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 `alert_enable` / `alert_disable`. The handler builds this exact\nobject on success."
    • removedOutput schema / properties / alert_id / description
      Removed value: -"The alert (indicator) ID that was toggled."
    • removedOutput schema / properties / enabled / description
      Removed value: -"New enabled state: `true` for enable, `false` for disable."
    • removedOutput schema / title
      Removed value: -"AlertToggleResponse"
  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 `alert_enable` / `alert_disable`. The handler builds this exact\nobject on success.",
+  "properties": {
+    "alert_id": {
+      "description": "The alert (indicator) ID that was toggled.",
+      "type": "string"
+    },
+    "enabled": {
+      "description": "New enabled state: `true` for enable, `false` for disable.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "alert_id",
+    "enabled"
+  ],
+  "title": "AlertToggleResponse",
+  "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
Behavior3/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description adds little behavioral detail. It does not clarify whether 'disable' is reversible or how it differs from deletion, but the idempotency annotation partially compensates for that gap.

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 one concise sentence with no filler. The core action and parameter are stated up front, and the helpful navigation hint follows naturally.

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 mutation tool with one required parameter and strong annotations, the description is nearly complete. The main gap is explaining the effect of disabling versus deleting an alertholistically, but the current text is adequate for a low-complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high at 100%, so the baseline is 3. The description adds value by specifying that alert_id is numeric and telling the agent where to find it, which improves the parameter semantics beyond the schema's generic 'Alert indicator id'.

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 states a specific verb ('Disable') and resource ('price alert') with the identifying parameter ('alert_id'), which clearly distinguishes it from sibling tools like alert_enable and alert_delete. It is immediately obvious what this tool does and which resource it acts on.

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?

It explicitly instructs the agent to use alert_list to find the numeric alert_id, providing useful operational guidance. It does not explicitly contrast when to use disable versus delete/enable, but the verb and id guidance make the intended usage clear enough.

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