Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_list_event_kinds

Lists every stock and crypto event kind and explains its default stream status, subscription support, timestamp meaning, and the fields usable in queries, selects, and grouping.

Instructions

Returns every event kind: what it is, whether it is in the default stream and can be subscribed to, what its ts means, and the fields you can name in q, select and group_by when you ask for that kind alone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tickerbot_list_event_kinds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countYesThe kinds in `kinds`.
kindsYesOne entry per kind.
_advisoriesNoPresent only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).
common_fieldsYesThe fields every event has, whatever its kind: `id` (stable across reads; use it to drop duplicates), `ticker`, `ts`, `kind`. Each as `name`, `type`, `description`, `nullable`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses the exact attributes returned per kind, including default-stream membership and subscribability, which are behavioral facts an agent needs before calling `tickerbot_subscribe_events`. It stops short of stating safety/read-only nature explicitly or any freshness/caching behavior, but "Returns" plus a fixed catalog implies a pure read.

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?

A single front-loaded sentence opening with the verb and resource, then a colon introducing the payload details. Every clause adds a distinct fact (identity, default stream, subscribability, `ts` semantics, queryable fields) with no filler or repetition.

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

Completeness5/5

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

For a zero-parameter catalog tool with an output schema present, the description supplies everything needed to decide when to call it and how to use the result. Return-value structure is covered by the output schema, and the description still highlights the most decision-relevant fields.

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 tool takes zero parameters, so the baseline is 4. The description goes slightly beyond by clarifying that `q`, `select` and `group_by` field names are per-kind and only valid "when you ask for that kind alone", which is contextual guidance even though those parameters belong to other tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns every event kind" gives a specific verb and resource, and the following clauses enumerate what each entry contains (semantics, default-stream membership, subscribability, `ts` meaning, nameable fields). It is clearly a discovery/catalog tool distinct from `tickerbot_list_events` or `tickerbot_query_events`, though it never names a sibling to make that contrast explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the schema-discovery call to make before querying or subscribing to events, since the description explains that field names for `q`/`select`/`group_by` depend on the kind. There is no explicit when-to-use statement, no exclusion, and no named alternative such as `tickerbot_list_events`.

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