Skip to main content
Glama

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

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuine context beyond that: the upstream source is SEC EDGAR 13F submissions and each call costs $0.50 USDC. The cost disclosure is materially useful for an agent deciding whether to invoke. It does not contradict any annotation.

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 use case, then return shape, source, hard requirement, and price in descending priority. No filler. The only mild redundancy is restating 13F provenance via 'Source: SEC EDGAR 13F submissions', which still adds value.

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?

With no output schema, the description must carry return-value burden, and 'delta summary scaffolding' is vague about what the agent actually receives beyond paired filings. The core decision inputs (cost, source, identifier requirement, read-only nature) are present, so it is adequate but leaves meaningful ambiguity about output shape.

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 description coverage is 0% and the JSON schema declares zero required parameters, so the description's 'Requires ticker or cik' actually adds a real gating constraint that the schema omits. However it does not say whether the two are mutually exclusive, which to prefer, or the expected CIK format (zero-padding, up to 12 chars), leaving half the semantics unresolved.

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, and adds what is returned (current and prior quarter filing pairs with a delta summary). An agent can tell this is a 13F holdings-comparison tool from the description alone, though it names no sibling to distinguish itself from.

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?

The opening 'Use when comparing institutional 13F-HR filing quarters for QoQ holdings change context' gives an implied trigger condition, but it largely restates the tool name. There are no when-not conditions, no prerequisites, and no named alternative for single-quarter holdings or non-institutional ownership data.

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