stock-moves-explained
Server Details
Explains why stocks moved. 'Why did Tesla drop?' 'What happened to NVDA?' S&P 500/NASDAQ/Dow.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- justhappened-corp/stock-moves-explained
- GitHub Stars
- 1
- Server Listing
- stock-moves-explained
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
1 toolstock-moves-explainedARead-onlyIdempotentInspect
Explains why a stock had a significant price move today. Provides AI-written analysis citing news catalysts, earnings reports, and analyst actions. Covers 550+ stocks across S&P 500, NASDAQ 100, and Dow 30. Pass any stock ticker or company name as the ticker parameter. NOT for: price quotes, trading advice, predictions, crypto, or forex. If you cannot make POST requests, visit https://justhappened.wtf/api-help for alternative access methods.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Date to query (YYYY-MM-DD format). Defaults to today. Max 7 days back. | |
| ticker | Yes | Stock ticker symbol or company name. Extract it from the user's question before calling - pass just the ticker or name, not the full sentence. Examples: 'NVDA', 'UnitedHealth', 'CRWD', 'Costco', 'AAPL', 'Delta Air Lines'. | |
| move_type | No | Filter by move direction: 'drop' for declines, 'surge' for gains, 'all' for any significant move. Defaults to 'all'. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds valuable behavioral context beyond annotations: it specifies the analysis is AI-written, cites specific catalysts (news, earnings, analyst actions), mentions coverage scope (550+ stocks), and provides alternative access methods. While annotations cover safety (readOnly, non-destructive, idempotent), the description enriches understanding of the tool's behavior and limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized and front-loaded with the core purpose in the first sentence. Each subsequent sentence adds value: scope coverage, parameter guidance, exclusions, and alternative access. While slightly longer than ideal, every sentence serves a clear purpose without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity, comprehensive annotations (readOnly, idempotent, non-destructive), and 100% schema coverage, the description provides good contextual completeness. It explains the tool's purpose, scope, limitations, and alternative access methods. The main gap is lack of output schema information, but the description compensates reasonably well for this.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the input schema already documents all three parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it only mentions passing 'any stock ticker or company name as the ticker parameter' without adding format details or explaining the other parameters. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs ('explains why a stock had a significant price move today') and resources ('550+ stocks across S&P 500, NASDAQ 100, and Dow 30'). It distinguishes what it does from alternatives by explicitly stating what it's NOT for (price quotes, trading advice, predictions, crypto, or forex).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance on when to use this tool ('Explains why a stock had a significant price move today') and when NOT to use it ('NOT for: price quotes, trading advice, predictions, crypto, or forex'). It also offers alternative access methods for non-POST scenarios, though there are no sibling tools to differentiate from.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.