Skip to main content
Glama
cstamigo-droid

equity-intel-mcp

equity_analyze_ticker

Read-onlyIdempotent

Aggregate insider trading, superinvestor holdings, and price context into a single confidence-weighted verdict with per-source breakdown.

Instructions

Run a full multi-source analysis of a stock and return one scored verdict.

Fans out to every available source in parallel (price context, insider Form 4 activity, superinvestor holdings) and blends the directional signals into a confidence-weighted verdict from -100 (Bearish/AVOID) to +100 (Bullish/BUY), with a per-source breakdown. Sources that have no data are reported as "no signal" and excluded from the score rather than guessed.

This is the primary tool — prefer it for "should I look at X?" questions; use the individual tools when you only need one dimension.

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

Returns: str: Markdown verdict with gauge, action, signal-breakdown table, and each source's one-line takeaway; or JSON with the full verdict + raw signals.

Examples: - "Give me a full read on Microsoft" -> ticker='MSFT' - "Should I be looking at PLTR?" -> ticker='PLTR'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: it fans out to sources in parallel, blends signals, and reports missing sources as 'no signal' without guessing. No contradictions.

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

Conciseness5/5

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

The description is well-structured with a clear main purpose, detailed explanation, and separate sections for args and returns. Every sentence adds value, and it's appropriately sized without being verbose.

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

Completeness5/5

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

Given the tool's complexity and available schema/annotations/output schema, the description provides sufficient context: it explains the composite analysis, handling of missing data, and output formats. No gaps.

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

Parameters4/5

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

Schema coverage is high (both parameters have descriptions in schema). The description adds value by providing usage examples and clarifying the ticker case-insensitivity and output format options, but it does not introduce new parameter semantics beyond what schema already provides.

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?

The description clearly states the tool runs a full multi-source analysis of a stock and returns a scored verdict. It specifies the output range (-100 to +100), the sources used (price context, insider Form 4 activity, superinvestor holdings), and how missing data is handled. It also distinguishes itself from sibling tools.

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

Usage Guidelines5/5

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

Explicitly states 'prefer it for "should I look at X?" questions; use the individual tools when you only need one dimension.' This provides clear guidance on when to use this tool versus alternatives.

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/equity-intel-mcp'

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