Skip to main content
Glama

get_intelligence_changes

Per-ticker change detector since an ISO timestamp across SEC filings (8-K/10-K/10-Q), 5-factor SB Score deltas, and Form 13F filings (clamped to 90 days max). $0.01.

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": {
      "ticker": "<ticker>",
      "since": "<since>"
    },
    "name": "get_intelligence_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesRequired ISO-8601 timestamp cutoff (e.g. 2026-11-17T00:00:00Z)
tickerYesUS stock ticker symbol (e.g. NVDA)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two genuinely useful traits — a 90-day clamp on 13F coverage and a $0.01 cost — but says nothing about permissions, rate limits, behavior when no changes exist, or what a 'change' record contains.

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?

A single dense sentence, front-loaded with the core purpose, with cost appended as a useful trailing token. The parenthetical 90-day clamp is terse enough to border on cryptic, costing it a point.

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 two-parameter read tool with full schema coverage and no annotations, the description covers the data sources, the time-scoping model, and cost — enough to call it correctly. Return-shape detail is the only real gap, and a change-detection tool's output is reasonably inferable from the enumerated sources.

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 coverage is 100%, so both parameters are already documented with types, examples, and the required flag; baseline 3 applies. The description adds only the 'per-ticker' scoping and a possible 90-day bound that may relate to the 'since' cutoff, but it is ambiguous whether the clamp constrains the timestamp or only 13F lookback.

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 verb+resource: a per-ticker change detector over three named data families (SEC filings 8-K/10-K/10-Q, SB Score deltas, Form 13F). This implicitly distinguishes it from single-source siblings like get_sec_8k_events and get_sb_score_history, though it never names an alternative explicitly.

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 'since an ISO timestamp' framing, which suggests a monitoring or refresh workflow. There is no statement of when to prefer this aggregate detector over the single-source siblings, and no exclusions or prerequisites.

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