Skip to main content
Glama

mcp-server

by io.github.tickerbot

tickerbot_list_universes

List universes — your saved ones and/or the built-in system universes (top_10, top_100). Filter with owner (like the signals catalog's kind): me (default, your own), system (built-ins), or all (both). Each row carries system: true|false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (applies to your own; system universes are a small fixed set returned in full on the first page).
ownerNoWhich universes to list.
cursorNoOpaque cursor.

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description adds valuable context: it mentions that each row carries 'system: true|false' and explains pagination behavior for system universes. However, it does not disclose read-only nature or authentication requirements.

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 highly concise, using only two sentences to convey purpose, filtering options, and response structure. No superfluous information.

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 description covers main behavior and filter logic, but does not explain the 'cursor' parameter or how pagination works beyond the limit note. For a 3-param tool with no output schema, some gaps remain.

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?

Despite 100% schema coverage, the description adds meaning beyond the schema by explaining the 'owner' default and the 'limit' behavior for system universes. This enhances understanding.

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 action (List) and resource (universes), and distinguishes between saved ones and built-in system universes, providing specific examples (top_10, top_100).

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 guidance on when to use this tool versus siblings like tickerbot_list_system_universes or tickerbot_get_universe. The description does not mention alternatives or when not to use it.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target distinct resource-action pairs, but get_ticker and get_ticker_history overlap (both return a single historical row via asof), and the four subscribe_* tools are thin wrappers around create_webhook, creating some ambiguity. Detailed descriptions mitigate but don't eliminate confusion.

Naming Consistency4/5

The tickerbot_ prefix and verb_noun pattern are consistent (create_*, get_*, list_*, delete_*, update_*), but subscribe_* deviates from create_* for webhooks, and scan/search_news are bare verbs. Overall predictable.

Tool Count2/5

35 tools is excessive for the domain; many could be consolidated (e.g., four subscribe_* variants into a single parameterized webhook creator, get_ticker/get_ticker_history into one). The breadth of data types justifies some volume, but this exceeds the 25-tool threshold for coherence.

Completeness5/5

Full lifecycle coverage for universes, custom signals, and webhooks; extensive read-side for tickers, series, bars, events, news, and scans. No critical dead ends: anything creatable can be updated/deleted/tested, and data lookups have appropriate query tools.

Resources