Skip to main content
Glama
sreerajkrishnank

tickertape-mcp

Get stock/ETF details

get_stock_details

Retrieve a detailed metric snapshot for any US stock or ETF, covering valuation, growth, profitability, dividends, and more, grouped by category.

Instructions

Get a detailed metric snapshot for a single US stock or ETF by ticker: valuation, growth, profitability, dividends, and more, grouped by category, with a link to its Tickertape page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker symbol, e.g. "NVDA" or "VOO".
metricsNoAdditional metric aliases to include beyond the default snapshot.
asset_typeNoWhether the ticker is a stock or ETF.stock
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Describes output snapshot and link, but does not disclose error handling, rate limits, authentication needs, or behavior for invalid tickers. Insufficient for a complete behavioral profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, efficient and without fluff. Covers key details but could benefit from structuring the metric categories (e.g., list). However, it remains clear and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, description lacks completeness. Does not specify return format, pagination, error behavior, or usage limits. For a single-ticker snapshot, more context (e.g., data refresh frequency) would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 3 parameters. Description reinforces that ticker is required and adds grouping by category, but does not significantly enhance parameter understanding beyond schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it retrieves a detailed metric snapshot for a single US stock or ETF. Mentions specific categories (valuation, growth, profitability, dividends) and a link to Tickertape page. Distinguishes from sibling tools like screen_stocks (screening) and search_stocks (search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly indicates it is for individual tickers, but does not explicitly state when to use alternatives or provide exclusions (e.g., for multiple tickers use screening tools). No guidance on prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sreerajkrishnank/tickertape-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server