QuantApe Markets

get_list_criteria

Read-only

Metadata for one stock screen (smart list): display name, short description, icon, category ids and parent screen. Always free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`list_id`	Yes	Screen id from list_smart_lists (e.g. day_gainers, todays_earnings).

Output Schema

TableJSON Schema

Name	Required	Description
`icon`	Yes
`list_id`	Yes
`updated_at`	Yes	Screen last rebuilt, ISO 8601 UTC
`parent_list`	Yes	Id of the screen this one refines
`category_ids`	Yes
`display_name`	Yes
`short_description`	Yes

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": {
+    "category_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "display_name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "icon": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "list_id": {
+      "type": "string"
+    },
+    "parent_list": {
+      "description": "Id of the screen this one refines",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "short_description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "description": "Screen last rebuilt, ISO 8601 UTC",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "list_id",
+    "display_name",
+    "short_description",
+    "icon",
+    "category_ids",
+    "parent_list",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The readOnlyHint annotation already communicates safety, and the description adds useful context by specifying that it returns metadata fields and is 'Always free.' No contradictions with annotations exist, but no additional behavioral traits such as rate limits or access conditions are disclosed.

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?

The description is a single front-loaded sentence that states the resource, the fields returned, and the cost-relevant note. Every part earns its place with no redundant wording.

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?

For a one-parameter read-only metadata operation with a complete input schema and an output schema, the description plus structured data fully equips the caller. The lack of sibling routing is a usage-guideline gap rather than a completeness gap.

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%: list_id is documented with its source ('Screen id from list_smart_lists') and concrete examples. The description adds no extra parameter meaning, so the baseline score of 3 is appropriate.

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?

The description names a specific resource ('Metadata for one stock screen') and enumerates the exact fields returned (display name, short description, icon, category ids, parent screen). It is distinguishable from list_smart_lists and get_smart_list_changes, though it does not explicitly name those siblings.

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

Usage Guidelines2/5

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

No explicit guidance is given about when to use this tool instead of get_smart_list or list_smart_lists. The only contextual hint is 'Always free,' which addresses cost rather than selection criteria, leaving the agent to infer usage from the name and sibling list.

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?