Skip to main content
Glama

Stratalize Intelligence

Get 13f Holdings Delta

get_13f_holdings_delta
Read-only

Use when comparing institutional 13F-HR filing quarters for QoQ holdings change context. Returns current and prior quarter filing pairs with delta summary scaffolding. Source: SEC EDGAR 13F submissions. Requires ticker or cik. $0.50 USDC per call.

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_holdings_delta"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNo
tickerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious operational context the annotations lack: the upstream source (SEC EDGAR 13F submissions) and a per-call price of $0.50 USDC, which matters for budgeting repeated calls. The gap is that 'delta summary scaffolding' implies the response may be structural rather than populated data, and the description never resolves that ambiguity.

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?

Four short sentences, front-loaded with the trigger condition, then return shape, source, input requirement, and price. Nothing is padded, but 'delta summary scaffolding' and the trailing '$0.50 USDC per call' fragment give the paragraph a slightly telegraphic, note-like texture rather than a clean prose spec.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema tool, the definition covers the trigger, the input constraint, the source, and the cost, which is enough to call it correctly. It is not complete enough to set expectations about the result: no word on whether periods are auto-selected or configurable, whether the delta covers all holdings or top positions, or what 'scaffolding' means for downstream parsing.

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

Parameters5/5

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

Schema description coverage is 0% and the schema itself has no required fields, so this sentence is the only place the agent learns that one of ticker or cik must be supplied. That is a real constraint the JSON Schema does not encode and it prevents a guaranteed-wasted paid call. Score docked only slightly because formats are unstated: no guidance on CIK zero-padding or ticker casing/normalization despite maxLength limits in the schema.

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: comparing institutional 13F-HR filing quarters to surface QoQ holdings change, sourced from SEC EDGAR. That is well beyond a restatement of the name, though the phrase 'delta summary scaffolding' is jargon that doesn't clarify what an agent actually receives. It also doesn't distinguish itself from any sibling by name, so differentiation rests on the reader knowing what the siblings do.

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 opening clause 'Use when comparing institutional 13F-HR filing quarters for QoQ holdings change context' gives an explicit use condition rather than leaving the agent to infer it. There are no when-not conditions and no named alternatives for adjacent tasks (e.g. single-quarter holdings vs. QoQ change), so it stops short of full routing guidance.

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