Skip to main content
Glama
Sign In

LunaTerminal

by com.lunaterminal
OverviewDiscussionsAdmin

13F holders of a stock

get_13f_holders
Read-onlyIdempotent

Which tracked institutional managers held a stock in their latest quarterly SEC 13F filings: value, shares, portfolio weight and whether they bought, added or reduced, plus managers that sold out.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_13f_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker symbol, e.g. NVDA, SPY or BRK.B. Index symbols use ^, e.g. ^GSPC.

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 readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds value beyond them by disclosing the shape of the result set: value, shares, portfolio weight, buy/add/reduce direction, and sold-out managers. It does not state result-size limits or filing lag, which would complete the picture given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that identifies the resource and then lists the returned fields in a compact clause. No filler, no repetition of the title, nothing that could be cut without losing information.

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 usefully compensates by enumerating the substantive return fields, which is the main thing an agent needs before calling. It falls slightly short by not indicating result volume or the reporting lag inherent in quarterly 13F data.

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?

Only one parameter (symbol), and the schema already documents it fully with examples and the index-symbol caret convention at 100% coverage. The description adds no semantics about the parameter, so baseline 3 applies.

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 (institutional managers' latest quarterly SEC 13F holdings of a stock) and enumerates the data returned, so the agent knows exactly what this retrieves. It lacks any explicit differentiation from the close sibling get_13f_insights, leaving the boundary between the two to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the sibling get_13f_insights, which by name sounds adjacent. The only implicit cue is 'latest quarterly', which hints at recency but does not tell an agent when to pick this over other holdings-related tools.

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

All LunaTerminal 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