mcp-server

tickerbot_list_universes

Every universe you can reference: your own named ticker lists and the built-in ones. owner: system lists the built-in universes (top_10, top_100); all lists both. Use a slug as universe on scan, signal, and subscribe tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Page size (applies to your own). Max 100.
`owner`	No	Which universes to list: `me` (your own), `system` (built-ins), or `all` (both).	me
`cursor`	No	Opaque cursor from the previous response.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes	Server time this response was assembled (ISO 8601).
`count`	Yes	Rows in this page.
`universes`	Yes	The universes in scope. Every row carries `system: true\|false`.
`next_cursor`	Yes	Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "description": "Server time this response was assembled (ISO 8601).",
+      "type": "string"
+    },
+    "count": {
+      "description": "Rows in this page.",
+      "type": "number"
+    },
+    "next_cursor": {
+      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.",
+      "type": "string"
+    },
+    "universes": {
+      "description": "The universes in scope. Every row carries `system: true|false`.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "as_of",
+    "count",
+    "next_cursor",
+    "universes"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedSep 17, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque cursor."New value: +"Opaque cursor from the previous response."

addedInput schema / properties / limit / default
```
Added value: +50
```

changedInput schema / properties / limit / description

Previous value: -"Page size (applies to your own; system universes are a small fixed set returned in full on the first page)."New value: +"Page size (applies to your own). Max 100."

addedInput schema / properties / owner / default
```
Added value: +"me"
```

changedInput schema / properties / owner / description

Previous value: -"Which universes to list."New value: +"Which universes to list: `me` (your own), `system` (built-ins), or `all` (both)."

Changed2 schema fields changedJul 28, 2026

changedInput schema / properties / limit / description

Previous value: -"Page size."New value: +"Page size (applies to your own; system universes are a small fixed set returned in full on the first page)."

addedInput schema / properties / owner

Added value: +{
+  "description": "Which universes to list.",
+  "enum": [
+    "me",
+    "system",
+    "all"
+  ],
+  "type": "string"
+}

First observedJun 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It explains the meaning of `owner: system` and `all`, and notes that `limit` applies to your own universes. However, it does not disclose pagination behavior beyond the cursor parameter, or whether the response includes metadata like total counts. The description is honest and consistent, but not deeply behavioral.

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 two sentences, front-loads the core purpose, and packs the key distinctions (`owner: system`, `all`, slug usage) into a compact space. Every sentence earns its place.

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?

The tool has an output schema, so return values are already documented. The description covers the purpose, the owner semantics, and the downstream use of the result. It could mention pagination behavior more explicitly, but the cursor parameter and output schema cover the essentials.

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%, so the schema already documents all three parameters. The description adds context by explaining the semantic difference between `me`, `system`, and `all`, and by noting that `limit` applies to your own universes. This is useful but not a major addition beyond the schema.

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 clearly states the tool lists universes (both user-owned and built-in), distinguishes the `owner` values, and explains the relationship to other tools. It uses a specific verb ('list') and resource ('universes'), and differentiates from siblings like `tickerbot_get_universe` by describing the enumeration behavior.

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?

The description explicitly explains when to use this tool: to reference universes, and how the `owner` parameter selects between `me`, `system`, and `all`. It also tells the agent that the resulting slug is used as `universe` on scan, signal, and subscribe tools, which is actionable guidance for downstream usage.

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

All mcp-server 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.