Gemral Edge

Cluster Insider Buying

audit_cluster_insider_buying

Cluster insider buying audit identifying multiple distinct company executives or directors purchasing stock within a synchronized window versus routine or isolated transactions. Sourced from securities regulatory filings of insider transactions. Read-only evidence.

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": "audit_cluster_insider_buying"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`ticker`	No	Stock ticker, e.g. MDLN, CRWV, AAPL (optional)

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

C2.8/5.0

Behavior1/5

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

The description explicitly says 'Read-only evidence,' but the annotations declare readOnlyHint=false, which indicates the tool is not read-only. That is a direct contradiction. Beyond the contradiction, the description does not clarify permissions, safety profile, or other behavioral traits.

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?

The description is compact and front-loaded: the main concept comes first, followed by the data source and a short safety note. Every sentence is relevant, though the final 'Read-only evidence' sentence is actively problematic rather than helpful.

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?

The description defines the concept adequately and an output schema exists, so return-value detail is not required. However, it leaves parameter guidance thin and contains a read-only claim that conflicts with the annotations, making the overall context incomplete for safe invocation.

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

Parameters2/5

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

The description does not mention either parameter. The schema documents ticker but leaves limit undocumented, so the description fails to compensate for the 50% schema description coverage. It adds no parameter meaning beyond 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?

The description states a specific audit concept: identifying multiple distinct executives or directors buying stock in a synchronized window, contrasted with routine or isolated transactions. That is clearer than tautology, but it does not directly differentiate this tool from any named sibling tool.

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 description implies when the concept applies by contrasting cluster buying with routine or isolated transactions, but it gives no explicit when-to-use guidance, prerequisites, or alternative tools to choose instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gemral Edge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.