Skip to main content
Glama
cstamigo-droid

market-data-mcp

market_analyze

Read-only

Combine real-time momentum, latest news, and earnings risk into a single scored verdict from -100 to +100 for any stock symbol.

Instructions

Composite market analysis: momentum score, news catalyst, and earnings proximity.

Combines real-time quote (momentum), latest news headline (catalyst), and earnings calendar (risk flag) into a single scored verdict. Each component degrades gracefully — if news or calendar are unavailable, only quote is used. Score: -100 (strong selling pressure) to +100 (strong upward momentum).

Args: params: symbol (str) and response_format ('markdown'|'json').

Examples: - "Give me a full read on Apple" -> symbol='AAPL' - "What's the momentum on NVIDIA right now?" -> symbol='NVDA' - "Analyze Tesla for me" -> symbol='TSLA'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. Description adds value by explaining graceful degradation (if components are unavailable), score range (-100 to +100), and the composite nature, providing useful behavioral context beyond annotations.

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?

Description is well-structured with an overview, behavioral details, and arguments/examples. It is somewhat lengthy but front-loaded with key information; every sentence serves a purpose.

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

Completeness4/5

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

Given the tool's composite nature, schema coverage, annotations, and output schema existence, the description adequately covers return values, parameter usage, and graceful degradation. No major gaps identified.

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?

Input schema already provides clear descriptions for both parameters (symbol and response_format). Description adds examples and clarifies response_format options ('markdown' vs 'json'), but does not add significant meaning beyond the schema.

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?

Description clearly states it performs composite market analysis combining momentum, news, and earnings. Verb ('analyze') and resource ('market') are specific, and the composite nature distinguishes it from sibling tools like market_quote or market_news.

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

Usage Guidelines4/5

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

Description explains it provides a combined score using quote, news, and calendar, implying use when a consolidated verdict is needed. However, it does not explicitly state when not to use it or point to alternatives like individual data tools.

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/cstamigo-droid/market-data-mcp'

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