Skip to main content
Glama

Arkanum Data: SEC insider trades

Tracked funds

list_funds
Read-only

The big funds and companies whose 13F holdings Arkanum tracks, with their SEC IDs for fund_holdings. Hobby and Pro.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, not open-world), and the description adds real context beyond them: the list is a curated set of 'big' funds only (not exhaustive), the records include SEC IDs, and availability is gated to Hobby and Pro tiers. It stops short of describing ordering or result size, but the plan-gating and scope limitation are valuable disclosures.

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?

Two short sentences, front-loaded with the resource and its contents, then the downstream use, then tier availability. No filler; every clause carries information.

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 zero-argument, non-destructive list tool with no output schema, the description covers identity, scope, record contents, and tier access. It could say whether the list is complete or paginated, but an agent can call it confidently as written.

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?

With zero parameters and 100% schema coverage, there is nothing for the description to compensate for. It still usefully explains what the SEC ID field in each record is for, tying the output to a downstream sibling.

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 the specific resource — the large funds and companies whose 13F holdings Arkanum tracks — and adds that each carries an SEC ID used by fund_holdings. It is a noun phrase rather than a verb-led statement, but an agent can still tell what it returns and roughly how it differs from siblings like fund_holdings or big_stakes.

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 implied rather than stated: by mentioning 'their SEC IDs for fund_holdings,' it hints that this is the lookup you call to obtain IDs before querying holdings. There is no explicit 'use this when…' or 'do not use for…' routing language, and no exclusions against alternatives such as get_company.

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