TraderSpy

get_trader_profile

Read-onlyIdempotent

Use this when the user needs one trader profile, including metrics and latest positions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`source`	No	Exchange the trader is on	binance
`traderId`	Yes	The trader ID
`timeRange`	No	Performance time range	30D
`rankingType`	No	Ranking snapshot type	ROI

Output Schema

TableJSON Schema

Name	Required	Description
`aum`	No
`mdd`	No	Maximum drawdown
`pnl`	No
`roi`	No
`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
`rank`	No
`source`	No
`winRate`	No
`avatarUrl`	No
`positions`	No	Currently tracked positions
`timeRange`	No
`smartScore`	No
`traderName`	No
`rankingType`	No
`topTraderId`	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

A3.5/5.0

Behavior3/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 covered. The description usefully adds that the response bundles metrics with latest positions, but says nothing about whether the profile is live or snapshot-based, or about default-driven behavior for timeRange/rankingType.

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 no filler, and the trigger condition comes first. It is arguably too terse for a tool with four parameters and an output schema, but nothing in it is wasteful.

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, the description need not explain return values, and annotations cover safety; it correctly focuses on the trigger and payload. The remaining gap is routing guidance among the many sibling retrieval tools, which leaves the definition slightly thin but functional.

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 clear descriptions and enums for source, timeRange and rankingType, so the schema carries the parameter burden. The description adds no syntax, defaults or interaction notes beyond what the schema already says, so baseline 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 ('one trader profile') plus the payload contents ('metrics and latest positions'), which separates it from list-style siblings like get_top_traders and get_positions. It stops short of naming those siblings explicitly, so differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this when the user needs one trader profile' gives a positive usage condition but no exclusions or alternatives. An agent must infer for itself when to prefer get_trader_position_history or get_top_traders over this tool.

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.