Skip to main content
Glama

mcp-server

by io.github.tickerbot
OverviewDiscussionsAdmin

tickerbot_create_universe

Create a named ticker list owned by your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOptional slug — becomes the universe's permanent handle everywhere (`?universe=`, subscribe `universe`, CRUD path). Pattern `^[a-z][a-z0-9_]{0,62}$` — starts with a lowercase letter, then lowercase letters/digits/underscore, 63 chars max; the value is trimmed and lowercased before validation. `top_10` and `top_100` are reserved for system universes and rejected with 400. Must be unique within your account. Generated (`u_…`) if omitted.
nameYesHuman-readable label, up to 80 characters. Display-only — never used to reference the universe.
tickersYesTicker symbols, up to 10,000. Validated against the active universe. `[]` is accepted — a shell universe you can fill later via PATCH.
descriptionNoFree-form notes, up to 500 characters. Stored as `""` when omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe slug — the universe's handle in `?universe=`.
nameYesDisplay label.
sizeYesMember count.
as_ofYesServer time this response was assembled (ISO 8601).
systemYes`false` — this is your universe.
tickersYesMembers, after this call.
created_atYesCreation timestamp.
updated_atYesLast modification timestamp.
descriptionYesFree-form notes; `""` when unset.
effective_atNoSystem universes only; absent on yours.
rebalance_methodNoSystem universes only; absent on yours.
next_rebalance_atNoSystem universes only; absent on yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Optional free-form notes."New value: +"Free-form notes, up to 500 characters. Stored as `\"\"` when omitted."
    • changedInput schema / properties / id / description
      Previous value: -"Optional slug (lowercase letters, digits, underscore). Auto-generated from name if omitted. Must be unique within the account."New value: +"Optional slug — becomes the universe's permanent handle everywhere (`?universe=`, subscribe `universe`, CRUD path). Pattern `^[a-z][a-z0-9_]{0,62}$` — starts with a lowercase letter, then lowercase letters/digits/underscore, 63 chars max; the value is trimmed and lowercased before validation. `top_10` and `top_100` are reserved for system universes and rejected with 400. Must be unique within your account. Generated (`u_…`) if omitted."
    • changedInput schema / properties / name / description
      Previous value: -"Human-readable name."New value: +"Human-readable label, up to 80 characters. Display-only — never used to reference the universe."
    • changedInput schema / properties / tickers / description
      Previous value: -"List of ticker symbols."New value: +"Ticker symbols, up to 10,000. Validated against the active universe. `[]` is accepted — a shell universe you can fill later via PATCH."
  3. Changed2 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Optional free-form notes.",
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Optional slug (lowercase letters, digits, underscore). Auto-generated from name if omitted. Must be unique within the account.",
+  "type": "string"
+}
  4. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only states that a list is created and owned by the account; it does not disclose id generation, slug validation, reserved names, ticker validation, empty-list acceptance, persistence behavior, or error semantics. Those details appear in the schema, not in the tool description.

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 concise sentence with the verb and direct object front-loaded and no filler. 'Owned by your account' adds relevant context without bloat. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a straightforward create operation and the input schema richly covers parameters and output schema exists, so the agent can construct a valid call. However, the description itself provides no usage guidance or behavioral context and there are no annotations, leaving some selection and expectation-setting gaps that a fuller description would fill.

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%; each of the four parameters is individually documented with constraints like the id pattern, reserved values, length limits, and ticker validation. The tool description adds no parameter-level meaning, but the baseline 3 is appropriate because the schema already does the heavy lifting.

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 names a specific action ('Create') and resource ('named ticker list') and clarifies ownership ('owned by your account'). This distinguishes it from sibling create tools like tickerbot_create_custom_signal and tickerbot_create_webhook, and from update/delete universe tools.

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?

There is no explicit when-to-use guidance, no mention of alternatives, and no exclusions such as 'use update_universe for modifications.' The only usage signal is the verb 'Create' and the tool name, so the agent must infer when this tool should be selected.

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

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