Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Signal Detail

signal_detail
Read-onlyIdempotent

Retrieve a specific signal's full strategy analysis, including fit scores, valuation scenarios, evidence sources, and related fact IDs, by providing its signal ID.

Instructions

Get one signal by ID (from signals). Same fields as the list, plus analysis — the full strategy analysis: fit scores, valuation scenarios, evidence sources and related fact IDs.

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.
signal_idYesSignal ID, e.g. "sign_992_1a00c9425c3_48ab". Get IDs from `signals`.

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": {
-    "SignalOutlook": {
-      "enum": [
-        "Strong bullish",
-        "Bullish",
-        "Neutral",
-        "Bearish",
-        "Strong bearish",
-        "Unknown"
-      ],
-      "type": "string"
-    },
-    "SignalStatus": {
-      "enum": [
-        "Pending",
-        "Active",
-        "Deleted",
-        "AiFailed",
-        "FilteredByManual",
-        "AiSubmitFailed",
-        "Unknown"
-      ],
-      "type": "string"
-    }
-  },
-  "properties": {
-    "analysis": {},
-    "analysis_price": {
-      "format": "double",
-      "type": "number"
-    },
-    "benchmark_price": {
-      "format": "double",
-      "type": "number"
-    },
-    "company_name": {
-      "type": "string"
-    },
-    "conservative_price": {
-      "format": "double",
-      "type": "number"
-    },
-    "created_at": {
-      "type": "string"
-    },
-    "expression": {
-      "type": "string"
-    },
-    "id": {
-      "type": "string"
-    },
-    "key_catalyst": {
-      "type": "string"
-    },
-    "key_fact_id": {
-      "type": "string"
-    },
-    "market": {
-      "type": "string"
-    },
-    "optimistic_price": {
-      "format": "double",
-      "type": "number"
-    },
-    "outlook": {
-      "$ref": "#/$defs/SignalOutlook"
-    },
-    "outlook_desc": {
-      "type": "string"
-    },
-    "recommend_by": {
-      "type": "string"
-    },
-    "status": {
-      "$ref": "#/$defs/SignalStatus"
-    },
-    "strategy_id": {
-      "type": "string"
-    },
-    "strategy_name": {
-      "type": "string"
-    },
-    "summary": {
-      "type": "string"
-    },
-    "symbol": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "updated_at": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "symbol",
-    "company_name",
-    "market",
-    "title",
-    "summary",
-    "strategy_id",
-    "strategy_name",
-    "recommend_by",
-    "expression",
-    "key_fact_id",
-    "key_catalyst",
-    "analysis_price",
-    "conservative_price",
-    "benchmark_price",
-    "optimistic_price",
-    "outlook",
-    "outlook_desc",
-    "status",
-    "created_at",
-    "updated_at"
-  ],
-  "type": "object"
-}New value: +null
  3. Addedv0.10.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds value by disclosing the additional `analysis` payload and its subcomponents (fit scores, valuation scenarios, evidence sources, fact IDs), which is behavior not inferable from annotations or schema.

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 sentences with zero redundancy. The core action and resource are front-loaded, followed by the distinguishing field description. Every clause 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 read-only fetch with one required parameter and no output schema, the description covers what the tool does, what the response contains, and where to get the ID. It doesn't address edge cases like missing signals or null analysis, but given the low complexity and rich annotations, this is sufficient.

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%, so both parameters are already documented. The description adds a useful hint that `signal_id` values come from `signals` and gives an example format, which helps an agent construct valid calls. This is a small but real increment over 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 opens with a specific verb-resource pair ('Get one signal by ID') and immediately grounds it in the `signals` list, explicitly distinguishing it from the sibling list tool. Naming the extra `analysis` field and its contents makes the tool's purpose unambiguous and differentiated from other detail tools.

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 tells the agent to source IDs from `signals` and implies this tool is for retrieving a single signal's full detail, while the list provides summary fields. It doesn't explicitly state 'use this when you need analysis' or list exclusions, but the context is clear enough for an agent to select it appropriately among siblings.

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