Skip to main content
Glama

SweetValueLab

A manager's 13F holdings

get_investor_holdings
Read-onlyIdempotent

One investment manager SweetValueLab tracks (Berkshire Hathaway, Pershing Square, Bridgewater and about 80 more) from its latest Form 13F filing on SEC EDGAR: the quarter and filing date, the portfolio's size, its 10 largest positions, and its 10 largest moves that quarter in past tense — bought, added, reduced or sold — with the shares before and after. Also when the next 13F is due. A 13F is filed up to 45 days after the quarter ends, so it shows what the manager held then. From public SEC filings, updated as managers file. Not investment advice.

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": {
      "manager": "<manager>"
    },
    "name": "get_investor_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
managerYesThe manager, firm or person: "Berkshire Hathaway", "Warren Buffett", "buffett", "Pershing Square". When several match, the answer lists them; ask again with one's `manager` value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the data source (SEC EDGAR public filings), freshness behavior (updated as managers file; 13F filed up to 45 days after quarter end), what the holdings represent point-in-time, and a not-investment-advice disclaimer. This is unusually rich behavioral context for an annotated tool.

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 front-loaded with scope and content, and most sentences earn their place. It is somewhat dense—the long first sentence packs multiple return fields—but there is no filler or repetition.

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

Completeness5/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 fully explains what will be returned (quarter, filing date, portfolio size, top 10 positions, top 10 moves with before/after shares, next due date). Annotations cover safety, the schema fully covers the single parameter, and the description adds data freshness and source context, so an agent has everything needed to call it correctly.

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 schema's own description already explains fuzzy matching, multiple results, and how to retry with a specific manager value. The tool description adds the scale of coverage (~80 managers) and a few examples, but does not add syntax or format semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb (retrieves) and resource (one manager's latest Form 13F holdings), and enumerates the exact contents: quarter, filing date, portfolio size, top 10 positions, top 10 moves, and next due date. This clearly distinguishes it from sibling get_13f_consensus, which aggregates across managers.

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?

The description establishes clear context—it returns data for ONE investment manager, not a consensus—and gives examples like Berkshire Hathaway and Pershing Square. However, it does not explicitly say when to prefer this over get_13f_consensus or other siblings, leaving that inference to the agent.

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