TraderSpy

get_trader_position_history

Read-onlyIdempotent

Use this when the user asks for closed trade history of a specific trader.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number
`limit`	No	Results per page
`source`	No	Exchange	binance
`traderId`	Yes	The trader ID

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
`url`	No	The trader's page on traderspy.app: positions, history and Follow
`data`	No	Closed positions, most recently closed first
`pagination`	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": "The trader's page on traderspy.app: positions, history and Follow",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedAug 20, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds almost nothing beyond that: no note about pagination behavior, the source/exchange dimension, result volume, or rate limits, and the 'closed' qualifier merely restates the purpose rather than disclosing new behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler and the trigger condition stated first. It is terse rather than padded, though the terseness is what leaves the other dimensions under-served.

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

Completeness3/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 schema documents all params. Still, for a paged history tool the description gives no hint about pagination, source selection, or how it differs from get_positions, leaving a modest gap for an agent deciding between siblings.

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% with four documented params including a source enum, so the schema carries the parameter burden. The description adds no syntax, default, or filtering guidance beyond the schema, which is the baseline-3 case.

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 ('closed trade history') scoped to 'a specific trader', which distinguishes it from siblings like get_positions (open positions) and get_trader_profile. It does not name a sibling explicitly, but the resource phrasing is specific enough to route correctly.

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 trigger is explicit: 'Use this when the user asks for closed trade history of a specific trader.' That is a clear context for invocation. No when-not conditions or named alternatives are given, so it falls 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.