TraderSpy

get_signals

Read-onlyIdempotent

Use this when the user asks for recent public AI crypto trading signals, optionally filtered by coin, importance, strategy (the preset that produced them, by name) or pagination. When the user names a count ("last 5 signals"), pass it as limit — the card view renders exactly what was fetched, so over-fetching shows more cards than the user asked for.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`coin`	No	Filter by coin symbol, e.g. BTC, ETH
`skip`	No	Offset for pagination
`limit`	No	Number of signals to return
`strategy`	No	Filter by the AI strategy (preset) that produced the signal — part of its name, words in order, case-insensitive, e.g. "ATR Squeeze" or "Triple Oversold". get_signal_stats (period 7d) lists the strategies that fired recently with their names; a filter that matches nothing answers with the closest names.
`importance`	No	Filter by signal importance	all

Output Schema

TableJSON Schema

Name	Required	Description
`tip`	No	Rare: one sentence about a TraderSpy feature this connector cannot do, with the page it leads to
`data`	No	Signals, newest first
`warning`	No	Set when a strategy filter could not be applied or matched nothing (with the closest preset names)
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 17, 2026

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

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "action": {
-          "description": "buy or sell",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "coin": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "createdAt": {
-          "anyOf": [
-            {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "number"
-                },
-                {
-                  "format": "date-time",
-                  "type": "string"
-                }
-              ]
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "id": {
-          "description": "Signal id — pass to get_signal_details",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "importance": {
-          "description": "high | medium | low",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "price": {
-          "description": "Price when the signal triggered",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "resolutionStatus": {
-          "description": "pending | stop | tp1_hit | tp2_hit | tp3_hit | profit_locked | expired",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "signalStrength": {
-          "description": "weak | moderate | strong | very_strong",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "strategyName": {
-          "description": "Preset that produced the signal",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "targets": {
-          "anyOf": [
-            {
-              "items": {
-                "additionalProperties": true,
-                "properties": {},
-                "type": "object"
-              },
-              "type": "array"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "description": "Take-profit and stop levels: { label, type, pct }"
-        },
-        "timeframe": {
-          "description": "Chart timeframe the preset evaluated, e.g. 4h",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "triggeredConditions": {
-          "anyOf": [
-            {
-              "items": {},
-              "type": "array"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "description": "buy or sell",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "coin": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "createdAt": {
+          "anyOf": [
+            {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "number"
+                },
+                {
+                  "format": "date-time",
+                  "type": "string"
+                }
+              ]
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "id": {
+          "description": "Signal id — pass to get_signal_details",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "importance": {
+          "description": "high | medium | low",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "price": {
+          "description": "Price when the signal triggered",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "resolutionStatus": {
+          "description": "pending | stop | tp1_hit | tp2_hit | tp3_hit | profit_locked | expired",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "signalStrength": {
+          "description": "weak | moderate | strong | very_strong",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "strategyName": {
+          "description": "Preset that produced the signal",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "targets": {
+          "anyOf": [
+            {
+              "items": {
+                "additionalProperties": true,
+                "properties": {},
+                "type": "object"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Take-profit and stop levels: { label, type, pct }"
+        },
+        "timeframe": {
+          "description": "Chart timeframe the preset evaluated, e.g. 4h",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "triggeredConditions": {
+          "anyOf": [
+            {
+              "items": {},
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "url": {
+          "description": "This signal's page on traderspy.app: chart, levels and outcome",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

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"
+}

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / strategy

Added value: +{
+  "description": "Filter by the AI strategy (preset) that produced the signal — part of its name, words in order, case-insensitive, e.g. \"ATR Squeeze\" or \"Triple Oversold\". get_signal_stats (period 7d) lists the strategies that fired recently with their names; a filter that matches nothing answers with the closest names.",
+  "type": "string"
+}

addedOutput schema / properties / warning

Added value: +{
+  "description": "Set when a strategy filter could not be applied or matched nothing (with the closest preset names)",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedAug 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With annotations already covering read-only, idempotent, non-destructive and closed-world behavior, the description earns credit by adding a non-obvious rendering trait: the card view shows exactly what was fetched, so over-fetching surfaces extra cards. It does not address rate limits or default result size (schema does), but the UI-side effect is genuine value beyond structured fields.

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, no filler. The activation condition is front-loaded and the higher-stakes subtlety (over-fetching in the card view) is placed immediately after the parameter it governs.

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 no explanation, and all five parameters are documented in-schema. The description covers triggering, filters, and the count-handling quirk, leaving only minor gaps such as pagination interaction with `skip`.

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 baseline is 3; the description goes beyond by explaining that `strategy` matches a preset name (words in order) and by prescribing the `limit` semantics for explicit user counts. That said, it repeats some schema content rather than adding syntax for `coin` or `importance`.

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 ('recent public AI crypto trading signals') and enumerates the filterable dimensions, so an agent can distinguish it from singular-lookup siblings like get_signal_details or aggregate siblings like get_signal_stats. It stops short of explicitly naming what it is not, so it does not reach the sibling-exclusion standard of a 5.

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?

Opens with an explicit trigger ('Use this when the user asks for recent public AI crypto trading signals') and gives concrete guidance for the count case ('last 5 signals' → pass as `limit`). It offers no when-not conditions, but the usage context is clear and actionable.

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.