Skip to main content
Glama

Get the Clearthesis investment thesis on a stock

get_stock_thesis
Read-only

Plain-English investment thesis on a US stock: what the business does and how it makes money, financial performance, moat and competition, management, a 1-to-5 quality scorecard, and key numbers, with sources. Includes a link to the full thesis, where Clearthesis gives its fair value estimate, five-year projections and verdict.

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": "get_stock_thesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol, for example NVDA or BRK-B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing what the response contains and, importantly, what it does not (fair value, projections, verdict are only reachable via the link). What it omits is equally notable: it never says whether any US ticker works or only coverage-list names, or what happens for an uncovered ticker.

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?

Two sentences, both doing work: the first enumerates deliverable content, the second sets the boundary between the summary and the paywalled full thesis. The comma-separated content list is dense but each item signals a distinct section an agent may want to quote. Minor cost is that the long unbroken list is harder to scan than a short bulleted form.

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?

With no output schema, the description carries the burden of describing the return value, and it does so thoroughly, section by section, plus the outbound link. For a single-parameter read-only lookup, the only material gap is coverage eligibility (whether the ticker must be on the covered list), which matters for correct invocation.

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?

Schema description coverage is 100% and there is a single required parameter, so the schema already explains the ticker format with an example (NVDA, BRK-B). The description adds nothing about ticker handling, exchange suffixes, or case sensitivity beyond that. Baseline 3 applies when the schema carries the semantics.

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?

The description names a specific resource (a plain-English investment thesis on a US stock) and enumerates its constituent parts: business model, financial performance, moat, management, a 1-to-5 scorecard, and key numbers. That is far more specific than the title alone. It stops short of distinguishing itself from siblings like get_stock_updates or search_stocks, so it is clear but not differentiating.

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?

No explicit when-to-use or when-not statement appears, and no sibling is named. However, the closing sentence carves out a real usage boundary: this tool returns the summary thesis plus a link, and fair value estimates and five-year projections live behind that link rather than in the response. That implies the right context for calling it without making the routing explicit.

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