MCP Server Demo
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 |
|---|---|
| get_stock_priceA | Fetch the latest stock price for a given ticker symbol from Yahoo Finance |
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 ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the sole operation available.
The single tool follows a consistent verb_noun naming pattern (get_stock_price). Since there are no other tools to compare, it inherently maintains perfect consistency.
One tool is too few for a server named 'MCP Server Demo' which suggests a broader demonstration purpose. It feels thin and limited, lacking coverage for related operations like historical data or portfolio management.
The server's domain appears to be stock data, but with only a price-fetching tool, there are significant gaps. Missing operations include historical prices, company info, or trading actions, making the surface severely incomplete for typical stock-related workflows.