Skip to main content
Glama
Sign In
openmarkets

openmarkets

by danchev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_insider_purchases

Retrieve insider purchase transactions for any stock ticker to monitor corporate insider buying activity.

Instructions

Retrieve insider purchases for a given ticker.

Args: ticker (str): The symbol of the security.

Returns: Any: Insider purchases data from the repository.

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>"
    },
    "name": "get_insider_purchases"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden but fails to disclose behavioral traits like data freshness, authorization needs, or any side effects. The return type is vaguely described as 'Any', and no details about the data structure are given.

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 very short (two sentences plus Args/Returns) and front-loaded, but the brevity sacrifices important details. It earns its place but could be more informative.

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

Completeness2/5

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

Given no output schema and no annotations, the description is incomplete. It does not explain the structure of the returned insider purchases data (e.g., fields, pagination) or any constraints, leaving the agent with significant uncertainty.

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

Parameters4/5

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

The description explains the ticker parameter as 'The symbol of the security', adding meaning beyond the schema which only has the title 'Ticker'. With 0% schema coverage, this significantly aids understanding.

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 verb 'Retrieve' and the resource 'insider purchases' for a given ticker, making the tool's purpose specific and distinguishable from sibling tools that retrieve other data types.

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?

The description does not provide any guidance on when to use this tool versus alternatives, such as get_institutional_holdings or get_major_holders, nor does it mention prerequisites or exclusion criteria.

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

Deploy Server

Other Tools