Skip to main content
Glama

insidergraph

by com.insidergraph

Company insider profile

company_profile
Read-onlyIdempotent

START HERE for any company question: one call returns the full insider picture for a ticker or company name - current 5%+ stakeholders (13D/13G), insider buy/sell activity (Form 4), announced sales (Form 144), and recent material events (8-K). Every row links its SEC filing; next_tools names the tool for each deeper question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAny identifier: ticker in any format (NVDA, NASDAQ:AAPL, $NVDA, BRK.B), company name, CIK number, US ISIN, or CUSIP.
window_daysNoLookback for insider activity, planned sales, and events; default 90.

TDQS

A4.7/5.0
Behavior5/5

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

The description adds behavioral context beyond the readOnly/idempotent annotations: it explains that every row links to its SEC filing, and that navigation to deeper tools is provided via next_tools. This gives the agent useful information about return format and workflow without contradicting annotations.

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?

The description is a single, highly informative sentence that front-loads the main directive 'START HERE'. It packs content types, return format details, and navigation guidance without unnecessary fluff. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description provides a complete picture for an aggregator tool: it lists all included data categories, mentions that rows link to filings, and provides a path to more detailed tools. The absence of an output schema is compensated by this rich description.

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% with descriptions for both query and window_days. The description's phrase 'ticker or company name' reinforces the query parameter but does not add new meaning beyond the schema. Therefore, baseline 3 is appropriate; no extra param semantics are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'START HERE for any company question: one call returns the full insider picture for a ticker or company name'. It enumerates the specific types of information (13D/13G, Form 4, Form 144, 8-K) and distinguishes itself from sibling tools by positioning as the aggregator and mentioning 'next_tools names the tool for each deeper question'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidance is given: 'START HERE' indicates this is the first tool to use. The phrase 'next_tools names the tool for each deeper question' points to alternatives and signals when more specific tools are appropriate. This effectively communicates when to use this tool versus siblings.

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

All insidergraph toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: per-form search tools (get_insider_trades, get_material_events, get_planned_sales, get_stakes), cross-feed signals (cluster_buys, planned_vs_executed, trades_before_events), and support utilities (company_profile, describe_coverage, find_company, list_recent_filings). The only slight overlap is company_profile vs. get_insider_trades, but company_profile is explicitly an aggregator that routes to detailed tools, eliminating ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern, especially the get_* family (get_insider_trades, get_material_events, etc.). However, three tools deviate: company_profile (noun_noun), planned_vs_executed (phrase with 'vs'), and trades_before_events (noun_phrase). These are still readable and clearly named, but they break the otherwise consistent convention.

Tool Count5/5

11 tools is well-scoped for the domain of insider trading analytics. It provides a complete set of per-filing-type search tools, cross-feed signals, and support utilities without redundancy or bloat. The count is within the ideal 5-15 range and feels justified.

Completeness5/5

The tool set covers the full lifecycle of insider data: entity resolution (find_company), orientation (describe_coverage), all major SEC forms (3/4/5, 8-K, 144, 13D/13G) via dedicated search tools, and advanced cross-feed analytics (cluster_buys, planned_vs_executed, trades_before_events). No obvious gaps are apparent for the stated purpose.

Resources