TraderSpy

This connector has been deprecated

Duplicate entry for the same endpoint. TraderSpy is actively maintained; this particular listing is simply not the one we keep current. Use TraderSpy instead: it is published from the official MCP registry, so its description and tool list refresh automatically with every release.

get_signal_stats

Read-onlyIdempotent

Use this when the user asks for aggregate AI signal performance statistics over a specific period — overall, or for one strategy (preset) by name. The answer also breaks the period down per strategy (byStrategy), which is how to learn the strategy names for get_signals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No	Time period for statistics	24h
`strategy`	No	Only the signals of one AI strategy (preset), matched by part of its name, case-insensitive.

Output Schema

TableJSON Schema

Name	Required	Description
`total`	No	Signals published in the period
`pending`	No	Still open at the end of the period
`stopped`	No
`warning`	No	Set when a strategy filter could not be applied or matched nothing (with the closest preset names)
`winRate`	No	targetHits / resolved, as a percentage; null when nothing resolved
`strategy`	No	The strategy filter that was applied, if any
`highCount`	No	High-importance signals
`byStrategy`	No	The same counts per strategy (preset) that fired in the period, most signals first
`targetHits`	No	Signals that reached a take-profit or locked profit

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

addedInput schema / properties / strategy

Added value: +{
+  "description": "Only the signals of one AI strategy (preset), matched by part of its name, case-insensitive.",
+  "type": "string"
+}

addedOutput schema / properties / byStrategy

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "pending": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "stopped": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "strategyName": {
+            "description": "The preset — pass it to get_signals as `strategy`",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "targetHits": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "total": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "winRate": {
+            "description": "targetHits / resolved, as a percentage; null when nothing resolved",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The same counts per strategy (preset) that fired in the period, most signals first"
+}

addedOutput schema / properties / strategy

Added value: +{
+  "description": "The strategy filter that was applied, if any",
+  "type": [
+    "string",
+    "null"
+  ]
+}

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.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds a genuine behavioral fact beyond that: the response breaks the period down per strategy (byStrategy), which shapes how the agent interprets output. It does not mention rate limits or failure modes, so not a 5.

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, front-loaded with the trigger condition, then the routing/output note. Every clause carries information and nothing is repeated from schema or annotations.

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?

With an output schema present, return-value detail is not required, and the description correctly spends its budget on trigger and routing context. It is nearly complete, missing only an explicit exclusion such as when to prefer get_signal_details instead.

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 adds meaning by clarifying the overall-vs-single-strategy semantics ('overall, or for one strategy (preset) by name'), which the schema does not state as the effect of omitting strategy. The case-insensitive partial-name matching is already in the schema, so no further credit there.

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 (get) and resource (aggregate AI signal performance statistics) with its scope (period, overall or one strategy). It is clearly distinguishable from get_signals, get_signal_details and get_market_stats, which cover raw signals rather than aggregates.

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?

The opening 'Use this when the user asks for...' gives an explicit trigger, and it routes the agent by noting the per-strategy breakdown is how to learn strategy names for get_signals. It lacks an explicit when-not-to-use or negative boundary against siblings, so it stops short of a 5.

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.

Resources

Need Help?