TraderSpy

get_signal_details

Read-onlyIdempotent

Use this when the user needs full details for one AI signal by ID, including review and resolution data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`signalId`	Yes	The ID of the signal to retrieve

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Signal id — pass to get_signal_details
`tip`	No	Rare: one sentence about a TraderSpy feature this connector cannot do, with the page it leads to
`url`	No	This signal's page on traderspy.app: chart, levels and outcome
`coin`	No
`price`	No	Price when the signal triggered
`action`	No	buy or sell
`history`	No
`targets`	No	Take-profit and stop levels: { label, type, pct }
`aiReview`	No
`createdAt`	No
`howToRead`	No	How the outcome was judged, in one sentence
`livePrice`	No	Current price, so the model can judge whether the signal still stands
`timeframe`	No	Chart timeframe the preset evaluated, e.g. 4h
`importance`	No	high \| medium \| low
`strategyName`	No	Preset that produced the signal
`signalStrength`	No	weak \| moderate \| strong \| very_strong
`indicatorValues`	No	Indicator readings at trigger time
`resolutionStatus`	No	pending \| stop \| tp1_hit \| tp2_hit \| tp3_hit \| profit_locked \| expired
`triggeredConditions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 17, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / tip

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "links": {
+          "anyOf": [
+            {
+              "items": {
+                "additionalProperties": true,
+                "properties": {
+                  "label": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "url": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "text": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Rare: one sentence about a TraderSpy feature this connector cannot do, with the page it leads to"
+}

addedOutput schema / properties / url

Added value: +{
+  "description": "This signal's page on traderspy.app: chart, levels and outcome",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedOct 12, 2026

changedOutput schema / properties / history / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "currentPrice": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "entryPrice": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "highestPrice": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "lowestPrice": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "resolution": {
-        "anyOf": [
-          {
-            "additionalProperties": true,
-            "properties": {},
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "{ status, price, time } once resolved"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "currentPrice": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "entryPrice": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "highestPrice": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "lowestPrice": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "resolution": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "properties": {},
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "{ status, at, price, stopAt? } once resolved: status = the highest take-profit reached before price touched the stop (stop | tp1_hit | tp2_hit | tp3_hit | profit_locked | expired); stopAt = price came back to the stop after that target, the signal ended there"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / howToRead

Added value: +{
+  "description": "How the outcome was judged, in one sentence",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedAug 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the payload includes 'review and resolution data', which is useful context beyond the annotations, but it does not cover error cases, permissions, or lookup-miss behavior.

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?

One front-loaded sentence beginning with 'Use this when...' with no redundant or filler content. 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?

An output schema exists, so return values need not be described, and the single parameter is fully covered by the schema. The description is sufficient for correct invocation, though it could note the list-vs-detail choice more explicitly given the many sibling tools.

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 there is a single required 'signalId' parameter whose type and meaning are fully documented in the schema. The description adds no format or sourcing detail beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb and resource: retrieves full details for a single AI signal by ID, and the phrase 'one AI signal' implicitly distinguishes it from the sibling list tool get_signals. It does not name a sibling explicitly, so it falls just short of the top score.

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?

'Use this when the user needs full details for one AI signal by ID' gives a clear triggering condition tied to a single-ID lookup. It offers no explicit when-not guidance or named alternatives (e.g., get_signals for lists), so it is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TraderSpy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.