Skip to main content
Glama
justin-hsun

ta-catalyst

by justin-hsun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TA_MODEYesOperation mode: 'stub' for fully offline fixture-based runs, 'real' for live models and data.
PINECONE_API_KEYNoAPI key for the Pinecone vector store used by the macro news search. Required when TA_MODE=real.
ANTHROPIC_API_KEYNoAPI key for Anthropic models. Required when TA_MODE=real.

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": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
history_move_analysisA

Explain what moved a stock over a past window, and why.

Runs three INDEPENDENT reads that are blind to each other, then reconciles them:

  1. A technical read of price and volume, with NO news context. Its value is that it is independent -- told the news first, a model narrates the chart to fit the story.

  2. A search of company-specific catalysts (earnings, guidance, ratings, legal, product).

  3. A deterministic read of the macro complex, then a search of macro news driven by what actually moved.

A deterministic scan first picks the significant trading days, so all three work from the same calendar. Each such day is then classified:

explained move with a matching catalyst unexplained a real move, news WAS searched, nothing found -- implies flow, positioning or genuine technical behaviour, and the technical read deserves MORE weight here overreaction move much larger than the catalyst warrants underreaction catalyst much larger than the move -- priced in no_ta / no_catalyst_coverage that stream was not run; NOT a finding about the market

Read coverage before the verdicts. A false there means the stream was never run, and absence of a search is not absence of a catalyst.

Turning every branch off returns coverage only, with no verdicts.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined, so an agent cannot misselect among alternatives.

Naming Consistency5/5

The single tool name follows a clean verb_noun pattern (history_move_analysis) and is descriptive of its functionality. Consistency is trivially maintained with one tool.

Tool Count3/5

A single tool feels thin for a server, even a specialized one. It is borderline acceptable given the complexity of the tool, but the calibration suggests 1-2 tools is on the low side.

Completeness5/5

The tool thoroughly covers the stated domain of explaining stock moves by integrating technical, catalyst, and macro analysis, with options to toggle branches. It provides a complete workflow for its narrow purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources