Skip to main content
Glama
clsung

Taiwan Stock Agent

by clsung

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_stock_dataC

Get detailed information about a specific stock.

get_price_historyC

Get historical price data for a specific stock.

get_best_four_pointsC

Get Best Four Points analysis for a specific stock.

get_realtime_dataC

Get real-time data for a specific stock.

get_market_overviewC

Get market overview information.

list_resourcesB

List all available MCP resources with templates and examples

subscribe_resourceC

Subscribe to resource updates for caching and notifications

invalidate_cacheC

Invalidate resource cache for fresh data

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
market://overview

TDQS

C2.8/5.0

Scored across 8 tools

Disambiguation3/5

The tools have some clear distinctions (e.g., market overview vs. stock-specific data), but there is notable overlap: get_stock_data, get_realtime_data, and get_price_history all target stock-specific information with ambiguous boundaries. get_best_four_points is distinct but could be confused as part of stock data. The descriptions help differentiate but don't fully resolve the ambiguity.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., get_market_overview, get_price_history, invalidate_cache), which is predictable and readable. However, list_resources and subscribe_resource deviate slightly by not starting with 'get', though they maintain the same snake_case style. This minor inconsistency keeps the naming mostly coherent.

Tool Count5/5

With 8 tools, the count is well-scoped for a stock analysis server, falling within the typical 3-15 range. Each tool appears to serve a distinct purpose in the domain, such as data retrieval, caching, and subscriptions, without feeling excessive or insufficient for the stated functionality.

Completeness3/5

The tool set covers core data retrieval (e.g., real-time, historical, overview) and utility functions (caching, subscriptions), but there are notable gaps: no tools for actions like buying/selling stocks, setting alerts, or analyzing trends beyond the 'best four points'. This limits agent workflows, as the surface is data-focused without operational capabilities.

Maintenance

ActivityInactive
ResponsivenessNo issues