Skip to main content
Glama

Search stocks covered by Clearthesis

search_stocks
Read-only

Find US stocks that Clearthesis has a full investment thesis on, by ticker or company name. Use this first to check whether a stock is covered.

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": {
      "query": "<query>"
    },
    "name": "search_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTicker or company name, for example "nvidia" or "COST"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 agent knows this is a safe, closed-domain lookup. The description adds useful scope ('US stocks', 'full investment thesis') beyond the annotations, but leaves open what happens when no match exists (empty results vs. error) and gives no sense of result shape or match breadth. With safety covered by annotations, a 3 is fair for the incremental context supplied.

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 short sentences, zero filler, with the coverage constraint and the 'use this first' directive both front-loaded. Nothing would be lost by keeping it, and nothing needs trimming.

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?

For a one-parameter read-only lookup with full schema coverage and no output schema, the definition covers purpose, domain scope, and call order adequately. The only meaningful omission is the no-match behavior, which matters when the tool's stated purpose is a coverage check.

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 coverage is 100% and the single 'query' parameter already carries its own description with examples matching the description's 'ticker or company name'. The description adds no new syntax, normalization, or partial-match guidance (e.g. whether 'nvid' matches), so the baseline of 3 applies.

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 states a specific verb and resource ('Find US stocks') and narrows the scope to companies Clearthesis has a 'full investment thesis' on, which is genuinely informative. It does not explicitly contrast itself with the sibling 'list_covered_stocks', so the boundary between searching for a known ticker and enumerating coverage is left to inference.

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

Usage Guidelines4/5

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

'Use this first to check whether a stock is covered' gives a clear entry-point directive and implies a workflow leading to get_stock_thesis. It stops short of naming the alternative ('list_covered_stocks') or stating when this tool is the wrong choice, so no explicit exclusions are provided.

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