Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Enable Price Alert

alert_enable
Idempotent

Activate a disabled price alert using its numeric alert_id from alert_list to resume notifications.

Instructions

Enable 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?

The description is consistent with annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) and adds no contradicting information. However, it contributes little behavioral detail beyond the verb 'enable' — the mutation, idempotency, and non-destructiveness are already carried by the annotations, and the description adds no new facts about side effects, errors, or state changes.

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 sentences with zero filler. The core action is front-loaded in the first sentence, and the second sentence earns its place by supplying the lookup cross-reference. Nothing could be removed without losing information.

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, no output schema, and annotations already covering idempotency and non-destructiveness, the description is essentially complete. The only minor gap is not addressing behavior when the alert doesn't exist or is already enabled — but the idempotentHint annotation partially mitigates this.

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 coverage is 100%, but the schema's alert_id description ('Alert indicator id') is weak and tautological. The tool description adds genuine value by specifying that the ID is numeric and by telling the agent exactly where to obtain it (alert_list). This exceeds the baseline expected when the schema already documents parameters.

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?

States a specific verb and resource — 'Enable a price alert by alert_id' — and the verb 'enable' distinguishes it from the sibling family (alert_add, alert_disable, alert_delete, alert_list) without needing to open any schema. An agent can tell exactly what this tool does and what it is not.

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?

Provides clear, actionable context by pointing the agent to alert_list as the source for the numeric alert_id — addressing the key precondition. However, it does not explicitly state when to choose this over alert_add (creating a new alert) or alert_disable (the inverse operation), so exclusion guidance is implied rather than stated.

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