Skip to main content
Glama

Kobo Terminal NGX

Director dealings (insider trades)

get_insider_dealings
Read-onlyIdempotent

Structured director-dealing filings: who bought or sold, role, volume, price, total value and holdings after the trade, plus weekly net insider flow and the most active tickers. Plan: Professional+. Professional and above get the full feed. Lower tiers receive a limited preview.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOnly filings from the last N days. Example: 30
sideNobuy or sell
limitNoMax rows, default 100, max 500
symbolNoFilter by ticker. Example: FIRSTHOLDCO

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior: the tool is gated at the Professional+ plan and lower tiers silently receive only a partial preview, which the agent must know to interpret thin results. Remaining gaps are pagination/ordering and how the preview manifests (truncation vs sampling).

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?

Three sentences, front-loaded with the data inventory before the entitlement caveat, with no filler. The only redundancy is 'Professional and above get the full feed' repeating the preceding 'Plan: Professional+', which costs a few words but no clarity.

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 carries the burden of describing return values, and it does so concretely by listing the fields present in each filing plus the aggregate flow and active-ticker views. For a four-parameter read-only feed this is close to sufficient; only pagination behavior and what a 'limited preview' contains are absent.

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 100%: days, side, limit and symbol all carry inline descriptions with examples and the 100/500 limit bounds. The description adds no parameter-level meaning such as whether side accepts only exact 'buy'/'sell', how days interacts with limit, or default ordering. Baseline 3 applies when the schema already does the explanatory work.

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 (structured director-dealing filings) and enumerates the payload fields an agent will get back: buyer/seller, role, volume, price, total value, post-trade holdings, plus weekly net insider flow and active tickers. That is far more than a restatement of the title. It stops short of distinguishing itself from adjacent tools such as get_block_trade_flow, which is the only missing element for a 5.

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 or when-not-to-use guidance and no mention of alternatives, even though get_block_trade_flow and get_disclosures sit in the same family. The plan-tier sentence ('Professional+', 'limited preview') is entitlement information, not usage routing, so the agent gets no help deciding whether this or a sibling tool fits the question.

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