Rozkoduj MCP

Official

by rozkoduj

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Strategy leaderboard

leaderboard

Read-only

Rank published backtested strategies by Rozkoduj Score, annualized USD returns, or recency. Filter by trading symbol to find top-performing strategies for a specific instrument.

Instructions

The strategy leaderboard - published, backtested strategies, ranked.

Use for "what are the best strategies?", "what works best on AAPL?". symbol narrows to strategies backtested on one instrument and makes best_run the best run on that instrument - case-insensitive, plain tickers just work (aapl finds aapl-us, btc finds btc-usd; the full slug like ry-ca pins one listing when a ticker trades in several markets).

There is NO risk filter here: unit_risk_band is returned on best_run but cannot be filtered or sorted on. Answer "best aggressive strategy?" by fetching a page and reading unit_risk_band, never by inventing a parameter.

Sorting: score_desc (default) ranks by the Rozkoduj Score - the headline leaderboard axis; apy_desc ranks by annualised return in USD (cagr_usd - the cross-market canon, immune to weak-currency inflation; local cagr is the fallback); recent is newest first.

Each item carries algorithm_uid (ULID), slug, i18n name/description, family/variant, and best_run with hot metrics: listing_slug (the instrument the metrics were earned on), cagr (APY in the instrument's local currency), cagr_usd (APY in USD - use this whenever comparing across markets), max_drawdown, win_rate_pct, num_trades, rozkoduj_score, rozkoduj_band, the risk mode (unit_risk_band, unit_risk_score), and a sparkline.

For one strategy's full dossier use strategy.

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	score_desc
`limit`	No
`family`	No
`offset`	No
`status`	No	active
`symbol`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv2026.8.15Aug 30, 2026

changedInput schema / properties / symbol / anyOf

Previous value: -[
-  {
-    "maxLength": 20,
-    "minLength": 1,
-    "pattern": "^[A-Za-z0-9.^=-]+$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 20,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9-]*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / visibility

Removed value: -{
-  "default": "public",
-  "enum": [
-    "public",
-    "all"
-  ],
-  "title": "Visibility",
-  "type": "string"
-}

addedOutput schema / $defs

Added value: +{
+  "LockedInfo": {
+    "additionalProperties": true,
+    "description": "Fields withheld for the caller's tier, carried inside a normal 200.",
+    "properties": {
+      "fields": {
+        "items": {
+          "type": "string"
+        },
+        "title": "Fields",
+        "type": "array"
+      },
+      "reason": {
+        "title": "Reason",
+        "type": "string"
+      },
+      "required_tier": {
+        "title": "Required Tier",
+        "type": "string"
+      },
+      "unlock_url": {
+        "title": "Unlock Url",
+        "type": "string"
+      }
+    },
+    "required": [
+      "fields",
+      "required_tier",
+      "unlock_url",
+      "reason"
+    ],
+    "title": "LockedInfo",
+    "type": "object"
+  },
+  "Strategy": {
+    "additionalProperties": true,
+    "description": "One published strategy. ``best_run`` stays an open object on purpose:\npinning the metric set here would make every added metric a breaking change\nin code that only forwards it.",
+    "properties": {
+      "algorithm_uid": {
+        "title": "Algorithm Uid",
+        "type": "string"
+      },
+      "aliases": {
+        "description": "i18n alias maps",
+        "items": {
+          "additionalProperties": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "title": "Aliases",
+        "type": "array"
+      },
+      "best_run": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Best Run"
+      },
+      "created_at": {
+        "title": "Created At",
+        "type": "string"
+      },
+      "description": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "description": "i18n",
+        "title": "Description",
+        "type": "object"
+      },
+      "family": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Family"
+      },
+      "is_active": {
+        "default": true,
+        "title": "Is Active",
+        "type": "boolean"
+      },
+      "locked": {
+        "anyOf": [
+          {
+            "$ref": "#/$defs/LockedInfo"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "name": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "description": "i18n: {en, pl}",
+        "title": "Name",
+        "type": "object"
+      },
+      "slug": {
+        "title": "Slug",
+        "type": "string"
+      },
+      "updated_at": {
+        "title": "Updated At",
+        "type": "string"
+      },
+      "variant": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Variant"
+      },
+      "version": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Version"
+      },
+      "visibility": {
+        "default": "public",
+        "title": "Visibility",
+        "type": "string"
+      }
+    },
+    "required": [
+      "algorithm_uid",
+      "slug",
+      "created_at",
+      "updated_at"
+    ],
+    "title": "Strategy",
+    "type": "object"
+  }
+}

addedOutput schema / description

Added value: +"One page of the leaderboard."

addedOutput schema / properties

Added value: +{
+  "items": {
+    "items": {
+      "$ref": "#/$defs/Strategy"
+    },
+    "title": "Items",
+    "type": "array"
+  },
+  "limit": {
+    "title": "Limit",
+    "type": "integer"
+  },
+  "offset": {
+    "title": "Offset",
+    "type": "integer"
+  },
+  "total": {
+    "title": "Total",
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "items",
+  "total",
+  "limit",
+  "offset"
+]

changedOutput schema / title

Previous value: -"leaderboardDictOutput"New value: +"StrategyPage"

Addedv2026.7.11Jul 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say `readOnlyHint: true` and `openWorldHint: false`. The description adds meaningful behavioral context beyond that: no risk filtering is possible, `unit_risk_band` cannot be filtered or sorted, `symbol` matching is case-insensitive with ticker normalization, and sort options have specific well-defined meanings. No contradiction with annotations exists.

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?

The description is long but well structured and front-loaded with the core purpose and usage examples. Every paragraph earns its place: symbol behavior, risk-filter caveat, sorting semantics, and return fields. A few clauses are somewhat redundant with the schema, but overall it is efficiently organized.

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?

The description covers the key operational details an agent needs: when to use the tool, how sorting works, how `symbol` affects `best_run`, what fields are returned, and an important limitation (no risk filter). An output schema exists, so the description need not restate return structures. This is complete enough for reliable invocation.

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?

With 0% schema description coverage, the description must compensate and does for the two most nuanced parameters: `sort` is fully explained with its enum meanings, and `symbol` gets detailed normalization semantics. However, `family`, `status`, `limit`, and `offset` receive little or no explicit textual explanation, though their schema titles and enum values make them partially self-explanatory.

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?

The description states a specific verb and resource: 'published, backtested strategies, ranked' on a leaderboard. It clearly differentiates from the sibling `strategy` tool by noting that a single strategy's full dossier belongs there, so an agent can distinguish the two without opening schemas.

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

Usage Guidelines5/5

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

It explicitly gives example user intents ('what are the best strategies?', 'what works best on AAPL?') and explains when `symbol` is appropriate. It also states when not to use this tool for risk filtering and directs users to the `strategy` tool for a full strategy dossier, providing clear when/alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server