Skip to main content
Glama

Which curated gurus hold this ticker

smart_money_holdings
Read-only

Returns every guru from our 60-name roster who held the requested ticker as of the latest 13F-HR quarter (or a specific historical quarter). Each row includes shares, USD value, % of portfolio, and the auto-classified delta vs the prior quarter. (GET https://app.deepvalues.ai/api/v1/smart-money/holdings, e.g. https://app.deepvalues.ai/api/v1/smart-money/holdings?ticker=AAPL — 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

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

Input Schema

NameRequiredDescriptionDefault
tickerYes
quarter_endNoISO date; default = latest available

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.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the data provenance (13F-HR filings), the cost (0.01 credits per call), credential-free rate limit (5 calls/day per address), and the exact shape of each row including the auto-classified delta. It also gives the concrete endpoint and a worked example, which lets an agent verify the request shape before calling.

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 core behavior is front-loaded in the first sentence, and the operational details (endpoint, credits, rate limit, fallback) are packed efficiently into parentheticals. The URL and query example are somewhat raw for prose but each element is actionable rather than filler.

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 properly compensates by enumerating the returned fields (shares, USD value, % of portfolio, delta). It leaves unstated how many gurus can return, whether results are paginated, and what an empty result means beyond the `request_data` pointer, which is a modest gap for a read-only lookup.

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 50% and the description does add meaning to `quarter_end` by framing it as a historical quarter rather than an arbitrary date, but it never explains the ISO date format or how a mid-quarter date is resolved. For `ticker` it only repeats the schema's AAPL example, so the description adds modest value over structured fields.

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?

The description names a specific verb and resource ('Returns every guru from our 60-name roster who held the requested ticker') and pins the temporal scope to 13F-HR quarters. That is clearly distinguishable from siblings like smart_money_changes or guru_portfolio without opening any schema.

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 states the two usage modes (latest available quarter vs a specific historical quarter) and routes the agent to `request_data` when a result is missing. It stops short of explicitly contrasting itself with smart_money_changes or guru_portfolio, so the agent must infer the boundary from the names alone.

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