FinDataMCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stock_priceB | Get the current stock price using yfinance. |
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 single tool has a clear, distinct purpose focused on retrieving stock prices.
The single tool name follows a clear verb_noun pattern (get_stock_price). With only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for a server named 'FinDataMCP', which suggests a broader financial data domain. This minimal toolset severely limits functionality and does not align with the implied scope of financial data operations.
The tool surface is severely incomplete for a financial data server. It only provides stock price retrieval, missing essential operations like historical data, financial statements, market indices, currency rates, or any other common financial data queries.