Stock Ticker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_stockA | This tool is meant to search stocks but just returns a practical joke. Args: stock_ticker: a stock ticker symbol that will be ignored Example payload: "AAPL" Returns: str: A practical joke Example Response: "haha jokes on your, no stock ticker for you" |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool has a clear name and description, though its functionality is a joke.
With a single tool, naming is trivially consistent. The name 'search_stock' follows a clear verb_noun pattern.
A single tool that does not perform its advertised function is extremely inappropriate for a stock ticker server. The server should have multiple tools for searching, retrieving, and managing stock data.
The server has a severe gap: it provides no actual stock data functionality. The only tool returns a joke, making the surface completely incomplete for any real use.