QuantApe Markets

get_smart_list_changes

Read-only

Which symbols entered or left a stock screen since its last recorded baseline (which can span several rebuilds) — e.g. new golden crosses, or names that dropped out of the momentum leaders. Free within your daily allowance (anonymous 5/day by IP, signed-in users 10/day, power users 50/day); beyond that $0.02 per call via x402 (USDC).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>"
    },
    "name": "get_smart_list_changes"
  }
}

Input Schema

Name	Required	Description	Default
`list_id`	Yes	Screen id from list_smart_lists whose additions and removals you want.

Output Schema

Name	Required	Description
`added`	Yes
`as_of`	Yes	Screen last rebuilt, ISO 8601 UTC
`list_id`	Yes
`removed`	Yes
`added_count`	Yes
`removed_count`	Yes
`baseline_as_of`	Yes	When the baseline was recorded; null = no baseline yet, so added/removed are empty

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "added": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "added_count": {
+      "type": "number"
+    },
+    "as_of": {
+      "description": "Screen last rebuilt, ISO 8601 UTC",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "baseline_as_of": {
+      "description": "When the baseline was recorded; null = no baseline yet, so added/removed are empty",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "list_id": {
+      "type": "string"
+    },
+    "removed": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "removed_count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "list_id",
+    "as_of",
+    "baseline_as_of",
+    "added",
+    "removed",
+    "added_count",
+    "removed_count"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint=true already covering the read-only safety profile, the description adds genuinely useful behavioral context: the baseline can span multiple rebuildsaine, and there is a daily free allowance with per-call overage pricing via x402 (USDC). No contradiction with annotations.

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 core behavior is front-loaded in the first clause, followed by useful examples and pricing details. It is a little dense as one long sentence, but every part earns its place and there is no filler.

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?

Given only one well-documented parameter, an output schema, and a readOnly annotation, the description is complete enough for an agent to invoke the tool correctly. It explains what the result represents, mentions the baseline semantics, and covers quota/cost constraints.

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?

The single parameter list_id is already fully described in the schema as 'Screen id from list_smart_lists whose additions and removals you want.' The description adds conceptual framing about stock screens and changes, but it does not materially extend parameter-level semantics beyond the schema, so the baseline of 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?

The description opens by stating exactly what the tool reports — symbols that entered or left a stock screen since its last recorded baseline — and illustrates with concrete examples such as new golden crosses and momentum-leader dropouts. This clearly distinguishes it from sibling tools like get_smart_list (current membership), get_smart_list_metrics, or list_smart_lists.

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 examples give a clear sense of when this tool is appropriate: detecting membership changes over a rebuild-spanning baseline rather than viewing the current list. However, it does not explicitly name sibling alternatives or state when not to use it, 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 QuantApe Markets 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?