Skip to main content
Glama

Material guru moves in a time window

smart_money_changes
Read-only

All 13F position changes meeting the materiality threshold (new positions, full exits, ≥25% share-count shifts, OR ≥$100M position size) across our entire 60-guru roster, in the requested window. (GET https://app.deepvalues.ai/api/v1/smart-money/changes, e.g. https://app.deepvalues.ai/api/v1/smart-money/changes?since=2026-Q1 — 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": {
      "since": "<since>"
    },
    "name": "smart_money_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesISO date OR YYYY-QN format. Filters on the QUARTER a position belongs to (quarter_end), not on when it was filed.
statusNo
filed_sinceNoOnly rows that reached us on or after this date (each row carries filed_at). Use it to poll for genuinely new 13F filings; `since` alone cannot tell a filing from this week from one made months ago in the same quarter.
min_position_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / filed_since / examples
      Added value: +[
      +  "2026-08-10"
      +]
    • addedInput schema / properties / min_position_usd / examples
      Added value: +[
      +  100000000
      +]
    • addedInput schema / properties / since / examples
      Added value: +[
      +  "2026-Q1"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond that: the concrete endpoint, the cost (0.01 credits per call), and anonymous access limited to 5 calls/day per address. It does not describe payload shape or pagination behavior, which is the remaining gap.

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 definition is front-loaded in the opening sentence, and every clause carries information (thresholds, endpoint, cost, auth limit, fallback). It is somewhat cramped into a single run-on with heavy parentheticals, which slightly hurts scanability.

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 read-only, open-world query tool with no output schema, the definition covers scope, filters, cost, and auth limits, and notes that each row carries filed_at. It stops short of describing the returned fields or result ordering, leaving some ambiguity about what an agent will receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage, the description compensates by stating the filterable materiality thresholds and roster-wide scope, and by reinforcing that `since` filters on the quarter a position belongs to rather than filing date. The four `status` enum values (new/added/trimmed/exited) are left undocumented in both description and schema description fields.

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 and operation – 13F position changes across the entire 60-guru roster – and spells out the exact inclusion criteria (new positions, full exits, ≥25% share-count shifts, or ≥$100M size). The 'entire 60-guru roster' phrasing implicitly contrasts with per-guru siblings such as guru_moves, but no sibling is named explicitly.

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 tells the agent when this tool applies (materiality-threshold moves in a window) and, via the schema text, distinguishes `since` from `filed_since` for polling new filings. It also routes to an alternative – 'Missing data? Call `request_data`' – but gives no explicit when-not guidance or comparison against smart_money_holdings.

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