Skip to main content
Glama
Sign In

SweetValueLab

by com.sweetvaluelab
OverviewDiscussionsAdmin

What the tracked managers hold in common

get_13f_consensus
Read-onlyIdempotent

Across the investment managers SweetValueLab tracks, from their latest quarter of Form 13F filings: the 10 stocks the most managers hold, the 10 the most managers bought or added to on balance, and the 10 the most reduced or sold on balance, each with the count of managers and the dollars moved. From public SEC filings, updated as managers file. Not investment advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the description needn't restate safety. It does add real value beyond them: data provenance (public SEC Form 13F filings), freshness ('latest quarter', 'updated as managers file'), and a disclaimer ('not investment advice'). It doesn't say what happens when no manager has filed for the current quarter.

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?

Front-loaded with the scope ('across the investment managers SweetValueLab tracks... latest quarter'), then enumerates the three lists. A single dense sentence plus short trailing clauses; the disclaimer earns its place in a financial context but adds minor length.

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 params and no output schema, the description carries the return-value burden and does so well: three named lists, each item including manager count and dollar movement. Minor gap: ordering within lists and treatment of managers who haven't filed is unstated, but an agent has enough to call it correctly.

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?

Zero parameters, so baseline is 4. The description correctly implies a no-input call and instead spends its words explaining the shape of the result.

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 verb and resource: consensus across tracked managers' latest 13F filings, returning three concrete top-10 lists (most held, most added, most reduced) with manager counts and dollars. It's clear what the tool produces, though it never names how it differs from sibling get_investor_holdings (per-manager view).

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?

Usage is implied by the content ('what managers hold in common'), so an agent can infer this is the aggregate view rather than a single-manager lookup. But there is no explicit when-to-use, when-not-to-use, or reference to the sibling alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SweetValueLab toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources