Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Fund Vote Matrix (every fund adviser's N-PX vote per ballot item at one meeting)

fund_vote_matrix
Read-onlyIdempotent

How every mutual fund adviser voted at one company's shareholder meeting, from SEC Form N-PX, as a matrix: one column per ballot item and one row per voting entity.

Columns: director elections split one column per nominee (matched on surname, so 'Ron Sugar' = 'Ronald D. Sugar'), with block votes in 'All nominees'; then the other proposals. Each column has the nominee or description, side (management / shareholder), category, fund votes, for_pct_by_shares (a fraction) and the 8-K result when linked. Rows: the fund adviser (by CRD), else the filer: name, crd, kind, family / family_cik (the 13F filer it reports under, by brand name, else MARS's adviser family), shares, n_against_mgmt, and per column For / Against / Abstain / Split / No vote with shares and fund counts (a split shows shares per side and the majority side).

Minor items (few votes) are hidden unless include_minor=true. For proposal-by-proposal tallies or a family rollup use company_fund_votes. Each row carries accessions (the entity's N-PX filings behind its votes, max 10; open with get_filing).

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

Input Schema

NameRequiredDescriptionDefault
cikNoCompany CIK (instead of ticker).
limitNoEntities to return (default 250, max 5000).
offsetNoEntities to skip.
tickerNoCompany ticker, e.g. MSFT (or give cik).
meetingNoMeeting date YYYY-MM-DD (default: the latest meeting with N-PX votes).
include_minorNoInclude minor ballot items (few votes) and entities that voted only on them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavior the annotations can't: minor items and entities voting only on them are suppressed by default, accessions are capped at 10, and split votes report shares per side plus a majority side. It does not discuss payload size or performance for the 5000-entity cap, which is the main remaining gap.

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?

Front-loaded with the one-sentence summary, then a labeled Columns/Rows breakdown and a closing alternatives pointer — good structure for a dense tool. The column and row sentences are long and stacked with clauses, so a bulleted split would read faster, but nothing is filler given there is no output schema.

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?

With no output schema, the description carries the full burden of the return shape and does so precisely — per-column fields (nominee/description, side, category, votes, for_pct_by_shares, linked 8-K result) and per-row fields (name, crd, kind, family/family_cik, shares, n_against_mgmt, per-item outcome). An agent can reason about the response and its semantics before calling.

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%, so cik/ticker/meeting/limit/offset/include_minor are already documented in structured fields. The description restates the include_minor default rather than extending it, and the surname-matching note ('Ron Sugar' = 'Ronald D. Sugar') concerns column construction, not any parameter. Baseline 3 is right when the schema does the heavy lifting.

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?

Opens with a specific verb+resource and scope: 'How every mutual fund adviser voted at one company's shareholder meeting, from SEC Form N-PX, as a matrix.' The title reinforces the grain (one row per voting entity, one column per ballot item), which makes it unmistakable against siblings like company_fund_votes or fund_equity_holders.

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?

Explicitly routes the agent away: 'For proposal-by-proposal tallies or a family rollup use company_fund_votes,' and points to get_filing for the accession numbers. It also states the default exclusion ('Minor items ... hidden unless include_minor=true'), so the agent knows when to flip that flag rather than inferring it.

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