mcp-server

tickerbot_get_universe

Returns the universe doc. Use top_10/top_100 to fetch a system universe; any other slug must be one your account owns.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Universe slug.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The slug — the universe's handle in `?universe=`.
`name`	Yes	Display label.
`size`	Yes	Member count.
`as_of`	Yes	Server time this response was assembled (ISO 8601).
`system`	Yes	`true` for a built-in universe, `false` for one you created.
`tickers`	Yes	Members.
`created_at`	Yes	Creation timestamp.
`updated_at`	Yes	Last modification timestamp.
`description`	Yes	Free-form notes; `""` when unset.
`effective_at`	No	System universes only: when this membership took effect.
`rebalance_method`	No	System universes only: how membership is chosen.
`next_rebalance_at`	No	System universes only: when membership is next recomputed.

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"
+    },
+    "created_at": {
+      "description": "Creation timestamp.",
+      "type": "number"
+    },
+    "description": {
+      "description": "Free-form notes; `\"\"` when unset.",
+      "type": "string"
+    },
+    "effective_at": {
+      "description": "System universes only: when this membership took effect.",
+      "type": "number"
+    },
+    "id": {
+      "description": "The slug — the universe's handle in `?universe=`.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display label.",
+      "type": "string"
+    },
+    "next_rebalance_at": {
+      "description": "System universes only: when membership is next recomputed.",
+      "type": "number"
+    },
+    "rebalance_method": {
+      "description": "System universes only: how membership is chosen.",
+      "type": "string"
+    },
+    "size": {
+      "description": "Member count.",
+      "type": "number"
+    },
+    "system": {
+      "description": "`true` for a built-in universe, `false` for one you created.",
+      "type": "boolean"
+    },
+    "tickers": {
+      "description": "Members.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "updated_at": {
+      "description": "Last modification timestamp.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "as_of",
+    "id",
+    "name",
+    "description",
+    "tickers",
+    "size",
+    "system",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedJun 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'Returns the universe doc' implies a read-only operation and the ownership constraint is stated, but failure behavior (e.g., what happens for a nonexistent or unauthorized slug), permissions, or side effects are not covered. This is minimally adequate for a simple GET-like tool.

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?

Two short sentences with no wasted words. The main action ('Returns the universe doc') is front-loaded, and the slug ownership constraint immediately follows. 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?

An output schema exists, so return values are already specified. The description covers the key operational constraint (slug ownership) and the special-case system universes. It could mention using tickerbot_list_universes to discover owned slugs, but that is more of a usage alternative than a missing requirement for correct 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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining that top_10/top_100 are special system slugs and that other slugs must be owned by the account, which goes beyond the schema's bare 'Universe slug' description and helps the agent choose valid inputs.

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 ('Returns') and resource ('the universe doc'), and clarifies the two categories of valid slugs (system universes like top_10/top_100 vs. account-owned). This distinguishes the tool from sibling list/create/delete universe tools and gives the agent a clear idea of what to expect.

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 description gives concrete guidance on acceptable slug values (system universes vs. account-owned) and implies that only owned slugs are fetchable. However, it does not explicitly name alternative tools (e.g., tickerbot_list_universes for enumeration or tickerbot_create_universe for creating), so the guidance stops short of explicit when/not-alternatives routing.

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.