Skip to main content
Glama

Structured human investment theses

theses
Read-only

Public investment theses with structured metadata — sentiment, conviction, price target, anchored DVI run. Filter by ticker, conviction, or sentiment. (GET https://app.deepvalues.ai/api/v1/theses — 0.01 credits per call; works with no credentials up to 5 call(s)/day per address) Missing data? Call request_data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "theses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerNo
sentimentNo
min_convictionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower, yet the description adds substantial context beyond them: the endpoint URL, a cost of 0.01 credits per call, and an unauthenticated allowance of 5 calls/day per address. Those cost/auth/rate-limit facts directly change how an agent should budget invocations.

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?

The content is front-loaded — resource and metadata first, then filtering, then operational constraints — and every sentence carries information. The parenthetical GET/credits/rate-limit clause is dense but not wasteful; minor cost is that it interrupts the reading flow.

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 four optional parameters, no output schema, and zero schema description coverage, the description does a fair job: it sketches the returned fields, the filtering surface, cost, auth limits, and the recovery path. The missing piece is limit/pagination behavior, which an agent needs to avoid over- or under-fetching.

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 0%, so the schema alone conveys only types and bounds; the description partially compensates by naming the three filter dimensions (ticker, conviction, sentiment). It never mentions the `limit` parameter, its default of 50, or the cap of 200, and does not explain that min_conviction is a 1-5 threshold, leaving real gaps.

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 the resource precisely ('public investment theses with structured metadata') and lists the metadata it carries (sentiment, conviction, price target, DVI run), so an agent knows what it gets back. The retrieval verb is only implied through 'Filter by ticker, conviction, or sentiment' rather than stated outright, which keeps it just short of a 5.

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?

It gives concrete filter conditions (ticker, conviction, sentiment) and an explicit fallback path — 'Missing data? Call request_data' — which routes the agent to a sibling. It does not state when another thesis-adjacent tool (e.g. sentiment, research) would be preferable, so no exclusion guidance is present.

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