Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Proxy Votes (meeting results, say-on-pay, next ballot)

company_proxy_votes
Read-onlyIdempotent

Shareholder-meeting vote results for one company (8-K Item 5.07) plus the items on the next ballot (DEF 14A filed after the latest result). Per meeting: each proposal with for/against/withheld/abstain/broker, support %, outcome, and whether it went against management; director elections are one row per nominee. Cards: last meeting, say-on-pay support and change vs prior, director support (per nominee: support %, withheld, slate average, lowest nominee, count under 80%), auditor ratification, shareholder proposals (5 years).

Rules (same as Kaleidoscope Console): support = for ÷ (for + against + withheld + abstain), broker non-votes excluded (ISS / Glass Lewis convention); withheld counts against and is also shown as its own number. Slate average = unweighted mean of the nominees' support %. Say-on-pay < 70% = warn (ISS responsiveness line); any nominee < 80% = warn. When a meeting's director table could not be split by nominee, director_support.granularity = 'slate' (one combined row). Directors are never marked failed by the vote count — they are plurality-elected and can stand below 50%. For say-on-pay and auditor votes the count overrides a contradictory extracted outcome (see outcome_note). A passing shareholder proposal or a failing management proposal is 'against management'. When the meeting date is missing or impossible the 8-K filing date is used (meeting_date_estimated=true).

Filings are returned by accession; open one 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": "company_proxy_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoMeetings lookback in years (default 10, max 25).
company_idNomars companies_v2 UUID (alternative to ticker_or_cik).
ticker_or_cikNoTicker or CIK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower, yet the description adds substantial behavioral detail: the exact support-percentage formula, ISS/Glass Lewis broker-non-vote exclusion, 70% say-on-pay and 80% nominee warning lines, the outcome_note override rule for say-on-pay and auditor votes, the granularity='slate' fallback when nominee splitting fails, and meeting_date_estimated when the meeting date is missing. That is precisely the kind of non-obvious semantics an agent cannot get from structured fields.

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 purpose and output inventory are front-loaded, and the dense rules block is genuinely load-bearing rather than filler. It is long and reads more like internal methodology documentation than a tool blurb, so a few sentences (the plurality-election aside for directors) could be trimmed, but nothing is truly wasted.

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?

This is a complex multi-card analytical tool with no output schema, and the description fully specifies return shape (proposals, support %, outcome, against-management flag, director rows per nominee, five-year shareholder proposals) plus edge-case flags. An agent has enough to call it correctly and interpret the response without opening the source filings.

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 years, company_id and ticker_or_cik are already fully documented in the schema, giving a baseline of 3. The description does not add format or precedence guidance beyond 'for one company'; it never says what happens if both company_id and ticker_or_cik are supplied, nor how lookback interacts with the next-ballot section.

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 opens with a precise verb and resource: shareholder-meeting vote results (8-K Item 5.07) plus next-ballot items from a post-result DEF 14A, scoped to one company. It even enumerates the per-proposal fields and card set, so an agent knows exactly what comes back. It does not explicitly differentiate itself from siblings like company_fund_votes or manager_proxy_voting, which keeps it off a 5.

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 by the data description (meeting results, say-on-pay, next ballot) and there is one concrete workflow hint: filings come back by accession and should be opened with get_filing. There is no explicit when-to-use versus company_fund_votes or manager_proxy_voting, and no statement of prerequisites for the company identifier.

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