Skip to main content
Glama

stock-deep-analysis

Stock deep analysis kit. The complete one-security methodology: verified price and financial metrics, payout history, business model, management, legal exposure, risk radar, red flags, and 3/5/7/10-year viability scenarios, with fund-mode handling for ETFs, mutual funds, and index funds. One call returns the full kit; the buyer's agent runs the analysis itself. Research, not investment advice. Price: $10.00 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "stock-deep-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesThe stock ticker to analyze, e.g. AAPL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It clearly discloses the paid per-call model ($10.00 USDC on Base via x402), the HTTP 402 response for unpaid calls, and that the output is research rather than investment advice. It does not cover rate limits, data freshness, invalid ticker behavior, or an explicit read-only/side-effect 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?

Front-loads the purpose and output categories, then covers the agent's role, disclaimer, and payment terms. It is dense but mostly earns its place; promotional phrasing such as 'complete' and 'kit' adds minor overhead.

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?

Without an output schema or annotations, the description lists the kit's components and explains payment behavior, which is enough to invoke correctly. It still lacks return format details, data recency/source notes, and invalid-input handling.

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?

The schema already documents the single ticker parameter at 100% coverage. The description adds meaning by noting fund-mode handling for ETFs, mutual funds, and index funds, expanding the ticker universe beyond the schema's 'stock ticker' wording.

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?

States a specific resource (a single security) and enumerates the analysis outputs: verified price and financial metrics, payout history, business model, management, legal exposure, risk radar, red flags, and viability scenarios. It also scopes asset coverage to stocks and funds, which distinguishes it from crypto-deep-analysis by asset class.

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?

Implies use for deep single-security research and notes fund-mode handling for ETFs, mutual funds, and index funds. However, it does not explicitly say when to choose this over alternatives or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources