Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Work This Deal (one desk deal: trail, vote, meetings, contacts, holder base)

deal_work
Read-onlyIdempotent

Work one Deal Desk deal (deal_id from deal_desk): the deal as the desk lists it, its stage (signed, proxy_filed (proxy or S-4), definitive_proxy, tender_open, voted, terminated, closed), the public trail per side (agreement, merger proxies, S-4 / F-4, tenders, delisting, 8-K items 1.01 / 1.02 / 2.01 / 5.01 / 5.07, each with accession and filing_url), holder vote results (for / against / abstain, for as a fraction of shares outstanding and of votes cast, turnout). Per listed side: whether its holders vote, its merger meeting from its own merger proxy (date, time, virtual, record date, vote required, majority of the minority, adjournment), solicitor and fee, transfer agent, law firms, bankers, agents, who to call (general counsel, corporate secretary, CEO, CFO), IR and media contacts from its press releases (name, title, IR firm, email, phone, source 8-K), and the solicitation sized up (shares outstanding, what a majority takes, institutions / insiders / everyone else as fractions, top 12 13F holders).

Deals leave the desk 90 days after signing.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "deal_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesA deal_id from deal_desk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured behavior: the full stage enumeration, the exact filing categories and 8-K item numbers returned, and the 90-day retention window after signing that determines data availability. It stops short of stating response size, pagination, or what happens for an expired/invalid deal_id.

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?

The content is front-loaded with the right framing ('Work one Deal Desk deal'), but the body is one enormous run-on sentence packing the stage list, filing taxonomy, vote metrics, advisor contacts and holder-base math into a single breath. Every element is arguably useful return-value information, yet the absence of any structure (bullets, grouping) makes it hard to scan, and the parenthetical item lists are dense.

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 and a rich, multi-section payload, the description carries the return-shape burden and does so thoroughly — an agent knows what sections to expect (trail, vote, per-side meeting/agents/contacts, solicitation sizing). The main residual gap is error/edge behavior: nothing says what is returned for a deal that has left the desk or an id that does not resolve, and no hint about response size for a tool returning 13F holders plus filing lists.

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 required parameter already documented at 100% schema coverage, and the description only restates its provenance ('deal_id from deal_desk'). That provenance is a small but real addition over the schema. No format, validation, or failure semantics for a stale/unknown id are given, so the baseline of 3 is right.

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?

States a specific verb and resource ('Work one Deal Desk deal') and then enumerates the scope precisely: stage taxonomy, filing trail per side, vote results, meeting/solicitor/advisor/contact details, and holder-base breakdown. It also anchors itself to the sibling that produces the identifier ('deal_id from deal_desk'), so an agent can distinguish it from deal_desk without opening either schema.

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: you must first call deal_desk to obtain a deal_id, and the closing line notes deals leave the desk 90 days after signing, which effectively bounds when this tool is usable. There is no explicit when-to-use/when-not guidance or named alternative (e.g. holder_profile, fund_vote_matrix) for agents who want only the vote or only the holders, so alternatives are left to inference.

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