Skip to main content
Glama
CatalystEdge

CatalystEdge

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
upcoming_eventsC

List curated upcoming catalysts with exact source and coverage limitations.

event_readinessC

Classify one catalyst as distant, preparation, pre-event, active, or resolved.

assess_eventC

Assess a user-supplied CPI, earnings, election, or other event as unverified.

assess_levelC

Explain a break, rejection, or test at a custom level from supplied OHLCV bars.

options_readinessC

Check whether event and options evidence are complete enough for human review.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 5 tools

Disambiguation3/5

Three tools center on evaluating events (event_readiness, assess_event, options_readiness), and an agent could initially struggle to pick between classifying a catalyst's lifecycle stage and assessing a user-supplied event. The descriptions do draw boundaries (classification vs. unverified assessment vs. evidence-completeness check), but the conceptual overlap keeps this from being clean.

Naming Consistency3/5

The set mixes noun-phrase names (event_readiness, options_readiness, upcoming_events) with verb_noun names (assess_event, assess_level), giving two distinct conventions within five tools. Names remain readable and snake_case throughout, but the pattern is not predictable.

Tool Count4/5

Five tools is well within the reasonable range for a narrow catalyst/event-readiness domain, and each tool maps to a distinct step in the workflow. The only minor concern is that the surface is thin enough that some tools feel like fragments of a larger lifecycle.

Completeness3/5

The set covers discovery (upcoming_events), classification (event_readiness), user-event assessment, evidence checking, and level analysis, but stops there. There is no way to fetch detail on a specific catalyst, register or track an event over time, or revisit resolved events, which are natural gaps for a catalyst-tracking server.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues