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.005 credits per call; works with no credentials up to 5 call(s)/day per address)

Input Schema

NameRequiredDescriptionDefault
limitNo
tickerNo
sentimentNo
min_convictionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable operational context: the exact endpoint, credit cost, and anonymous usage limit of 5 calls/day, which are not present in annotations or schema.

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 description is compact and front-loads the resource and filters before the operational parenthetical. It is efficient, though the parenthetical stacks endpoint, cost, and rate limit densely and includes unexplained jargon like 'anchored DVI run'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should do more to explain return shape, ordering, or pagination behavior. It names metadata fields (sentiment, conviction, price target, DVI run) but leaves the full response contract and limit behavior implicit.

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 description must compensate. It mentions ticker, conviction, and sentiment filters, adding some semantic meaning, but omits the limit parameter entirely and does not clarify that 'conviction' maps to min_conviction with a 1–5 threshold.

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?

States a specific resource — public human investment theses with structured metadata — and names the filterable fields. It is clear what the tool returns, but it does not explicitly differentiate itself from siblings like sentiment, research, or verdict.

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?

The description implies usage by listing filters (ticker, conviction, sentiment), but gives no explicit guidance on when to choose this over sibling tools such as sentiment or research. The agent must infer the use case from the resource name and fields.

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