TraderSpy

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
`url`	No	The signal feed on traderspy.app, every signal listed with its outcome
`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
`howToRead`	No	How an outcome is judged and what winRate counts; quote it when the user asks how the statistics work
`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.

Changed2 schema fields changedOct 17, 2026

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

addedOutput schema / properties / url

Added value: +{
+  "description": "The signal feed on traderspy.app, every signal listed with its outcome",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 12, 2026

addedOutput schema / properties / howToRead

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How an outcome is judged and what winRate counts; quote it when the user asks how the statistics work"
+}

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

Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does: the response includes a per-strategy breakdown (byStrategy), and that breakdown can be exploited to discover valid strategy names for get_signals — genuinely useful behavior not conveyed by 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 no filler, front-loading the trigger condition before the secondary routing tip. Every clause earns its place, including the pointer to get_signals.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 annotations cover the safety profile. With full schema coverage plus an explicit use trigger and a sibling routing tip, an agent has everything needed to select and invoke this tool correctly.

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 coverage is 100% and both parameters are documented in the schema (including the partial, case-insensitive strategy matching and the period enum), so the schema carries the parameter burden. The description restates that filtering can be overall or by strategy name but adds no syntax or format detail beyond the schema — baseline 3 applies.

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 ('aggregate AI signal performance statistics') plus the scoping options (overall or one strategy by name), which cleanly separates it from the sibling get_signals that returns raw signals. The cross-reference to get_signals for strategy names further disambiguates the pair.

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 triggering condition ('Use this when the user asks for aggregate AI signal performance statistics over a specific period'), which is strong when-to-use guidance. It implies but never states the inverse exclusion (e.g. don't use this to fetch individual signals), so it falls short of a full when/when-not/alternatives statement.

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.