Skip to main content
Glama

equity_analysis

Analyze US stocks and ETFs to receive buy/hold/sell signals, upside to analyst targets, P/E, EPS, health flags, and AI-driven analysis.

Instructions

Equity intelligence: buy/hold/sell signal, upside % to analyst target, P/E, EPS, health flags, AI analysis. US stocks and ETFs. Cached 30 min.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description must cover behavioral traits. Mentions caching (30 min) and AI analysis, but omits authentication needs, rate limits, or potential delays.

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?

Two sentences, no fluff. First sentence lists outputs, second adds scope and caching. Efficient and well-structured.

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?

Covers key outputs and caching behavior. With an output schema likely detailing return shape, description is sufficient. Missing rate limits but acceptable for a simple query tool.

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?

Input schema has one parameter (ticker) with 0% coverage. Description adds meaning by specifying 'US stocks and ETFs', guiding the agent on valid ticker values.

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

Purpose4/5

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

Clearly describes outputs (buy/hold/sell, upside %, P/E, etc.) and scope (US stocks and ETFs). However, uses noun phrase 'Equity intelligence' instead of a specific verb like 'provides'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like tech_analysis or news_sentiment. Only implicitly through scope (US stocks/ETFs). Lacks exclusion criteria or prerequisites.

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/Homie4570/lso-mcp'

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