mcp-server

tickerbot_update_universe

Update one of your universes: its name, description, or members. tickers replaces the whole list; add/remove adjust it. System universes cannot be edited.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Universe slug.
`add`	No	Add these tickers (deduplicated).
`name`	No	New label. Non-empty, max 80 characters.
`remove`	No	Remove these tickers.
`tickers`	No	Replace the full ticker list (up to 10,000; validated against the active universe). Does not combine with `add`/`remove` (400).
`description`	No	New notes. Max 500 characters.

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	`false` — this is your universe.
`tickers`	Yes	Members, after this call.
`created_at`	Yes	Creation timestamp.
`updated_at`	Yes	Last modification timestamp.
`description`	Yes	Free-form notes; `""` when unset.
`effective_at`	No	System universes only; absent on yours.
`rebalance_method`	No	System universes only; absent on yours.
`next_rebalance_at`	No	System universes only; absent on yours.

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; absent on yours.",
+      "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; absent on yours.",
+      "type": "number"
+    },
+    "rebalance_method": {
+      "description": "System universes only; absent on yours.",
+      "type": "string"
+    },
+    "size": {
+      "description": "Member count.",
+      "type": "number"
+    },
+    "system": {
+      "description": "`false` — this is your universe.",
+      "type": "boolean"
+    },
+    "tickers": {
+      "description": "Members, after this call.",
+      "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"
+}

Changed3 schema fields changedSep 17, 2026

changedInput schema / properties / description / description

Previous value: -"New notes."New value: +"New notes. Max 500 characters."

changedInput schema / properties / name / description

Previous value: -"New label."New value: +"New label. Non-empty, max 80 characters."

changedInput schema / properties / tickers / description

Previous value: -"Replace the full ticker list."New value: +"Replace the full ticker list (up to 10,000; validated against the active universe). Does not combine with `add`/`remove` (400)."

AddedJun 29, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden. It does disclose important behavior: system universes are locked from editing, and `tickers` overwrites the full list while `add`/`remove` adjust it incrementally. Missing are mutation side effects, permission requirements, or error behavior on invalid or protected universes; for a write tool this is only partial transparency.

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 tight sentences, no filler. The first sentence front-loads the action and scope; the second packs the mutation modes and the hard system-universe restriction. Every clause contributes meaning, making this an efficient definition.

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 description covers the core operations, parameter semantics, and a critical business rule (system universes cannot be edited). With full parameter schema coverage and an output schema available, the remaining gaps—like explicit error handling or alternative routing—are minor but keep it from being fully complete for a mutation tool with no annotations.

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?

The input schema already documents every parameter (100% coverage), so the baseline is 3. The description adds value by grouping parameters into names/description vs members and explicitly clarifying the semantic relationship between `tickers` (replace) and `add`/`remove` (adjust), which is not obvious from individual parameter descriptions alone.

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: 'Update one of your universes', and enumerates the editable aspects: name, description, or members. This clearly distinguishes it from sibling create/delete/get universe tools and from update_custom_signal/update_webhook by resource type. The scoping is precise and unambiguous.

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?

It gives clear context on when to use the tool: updating existing universes, and provides an explicit exclusion: 'System universes cannot be edited'. It also explains the internal choice between `tickers` (replace all) and `add`/`remove` (adjust). However, it does not explicitly name alternatives like create_universe for new universes, so it stops short of full route-guiding.

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.