Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Merger Votes Calendar (desk votes, merger meetings ahead, recent merger votes)

merger_votes_calendar
Read-onlyIdempotent

Merger votes in three lists. desk_votes: every Deal Desk deal whose holders vote or consent (stage, latest merger proxy, each voting side's meeting with solicitor and fee, the result once held); votes ahead first by date, then voted / closed / terminated. meetings_ahead: every company's merger meeting still ahead, market-wide, from merger proxies (date, time, virtual, record date, vote required, majority of the minority, solicitor and fee, proxy accession and filing_url), joint-proxy duplicates dropped. recent_votes: merger approvals voted in the last 30 days (outcome, votes for / against / abstain, for as a fraction of shares outstanding and of votes cast, turnout).

Use deal_work(deal_id) for one deal's full picture.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per list (default 100, max 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 safety profile is covered. The description adds real behavioral context beyond that: joint-proxy duplicates are dropped, results are ordered by date then status, and recent_votes is capped at 30 days. It does not state truncation risk from the limit parameter or whether lists are independently capped, which matters for a calendar-style aggregation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and information-dense with no filler sentences, but the three parenthetical field enumerations are packed into one run-on block separated by semicolons, which is harder to scan than a short bulleted breakdown per list. Nothing should be cut, but the structure could be clearer.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, enumerating the fields of each of the three lists (dates, record date, vote required, majority of the minority, fee, filing_url, vote tallies, turnout). The only gap is how limit interacts with three simultaneous lists and whether any list can be empty.

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?

There is a single optional limit parameter with 100% schema description coverage including default 100 and max 500. The description adds no meaning beyond the schema and does not say whether the limit applies per list or across all three, which is the one ambiguity a caller would care about. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States the resource (merger votes) and decomposes it into three named lists (desk_votes, meetings_ahead, recent_votes) with enumerated contents for each, so an agent knows exactly what comes back. The verb is implicit ('in three lists') rather than an explicit 'returns/lists', and it is differentiated only against deal_work, not against related siblings like company_proxy_votes or catalyst_calendar.

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

Usage Guidelines4/5

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

Explicitly routes single-deal lookups to deal_work(deal_id), which gives a clear alternative and the condition selecting it. It also states ordering semantics per list (votes ahead first by date, then voted/closed/terminated; 30-day window for recent_votes), which implicitly tells the agent which list answers which question. No explicit exclusions relative to other vote/calendar tools.

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