Skip to main content
Glama

Insider Activity Summary

insider_summary
Read-only

Rolled-up monthly insider buy/sell activity (net shares, dollar volume, transaction counts) for one bank's registrant. (Source: SEC Form 4 (aggregated).)

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "insider_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine context by naming the data source (SEC Form 4, aggregated) and the shape of the aggregate (net shares, dollar volume, counts). It does not disclose the freshness/lag of the monthly rollup or what happens when a registrant has no insider activity, which are the remaining behavioral gaps.

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?

One front-loaded sentence stating the aggregation granularity, the metrics, and the scope, plus a short source attribution. Nothing is wasted and the most decision-relevant words come first.

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?

For a simple one-parameter read tool with annotations covering its safety profile and no output schema, the description adequately explains what comes back and where it comes from. Only minor gaps remain around data recency and empty-result handling.

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?

There is a single parameter with 100% schema description coverage ('Federal Reserve RSSD id'), so the schema carries the burden and 3 is the baseline. The phrase 'for one bank's registrant' mildly clarifies that the id scopes to a single institution, but adds no new syntax or format detail.

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 and transformation: monthly insider buy/sell activity rolled up into net shares, dollar volume, and transaction counts for one bank's registrant. The words 'rolled-up' and 'aggregated' implicitly distinguish it from the transaction-level sibling sec_insider_txns, but that sibling is never named, so differentiation is inferred rather than stated.

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 only implied by the aggregation framing: an agent can infer this is for summarized monthly flows rather than individual filings. There is no explicit statement of when to prefer this over sec_insider_txns, no prerequisites, and no exclusions.

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