Public.com MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_event_summary

Read-only

Browse prediction-market event contracts one page at a time, filtering by category, frequency, or resolution time and returning event symbols, titles, volume, and status flags.

Instructions

Browse event contracts (prediction-market events), one page at a time.

Returns up to 100 events per page, each with its eventSymbol, title, volume, resolution time, resolved/halted flags, category and contract symbols. Pass an eventSymbol to get_event_details for its outcomes, YES/NO contracts and pricing. Results can include resolved and halted events. When the response carries a nextToken, call again with the same arguments plus that next_token to fetch the next page; it is absent on the last page.

eventSymbol (e.g. "KALSHI.KXBALANCESHEET-EO26") is the discovery identifier. It is NOT the "-EVENT" id that get_event_contract_bars takes.

Args: sorting_mode: VOLUME (default), EXPIRATION, or RECENTLY_ADDED. category: Only events in this category (from get_event_categories). subcategory: Only events in this subcategory. event_symbols: Only these events, by eventSymbol. frequencies: Only events recurring at these frequencies. Any of ALL, ONCE, FIFTEEN_MINUTES, ONE_HOUR, ONE_DAY, ONE_WEEK, ONE_MONTH, ONE_YEAR. resolution_time_start: Only events resolving at or after this ISO 8601 timestamp (e.g. 2026-12-31T00:00:00Z). resolution_time_end: Only events resolving at or before this ISO 8601 timestamp. display_resolved_events: Include (true) or exclude (false) resolved events. Omit for the API default. created_within_days: Only events created within the last N days. next_token: The nextToken from the previous page, to fetch the next one.

Input Schema

TableJSON Schema

Name	Required	Default
`category`	No
`next_token`	No
`frequencies`	No
`subcategory`	No
`sorting_mode`	No	VOLUME
`event_symbols`	No
`created_within_days`	No
`resolution_time_end`	No
`resolution_time_start`	No
`display_resolved_events`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.0Oct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With readOnlyHint/openWorldHint/destructiveHint already covering the safety profile, the description adds real behavioral detail beyond the annotations: a 100-item page cap, nextToken present-until-last-page semantics, the fact that resolved and halted events can appear in results, and that omitting display_resolved_events falls back to the API default.

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 purpose, then return shape, then sibling routing, then an arg list — a clean progression. It is somewhat long and the pagination theme is stated twice ("one page at a time" and the nextToken paragraph), but no sentence is filler.

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?

For a 10-parameter, all-optional filter tool with an output schema and annotations, everything an agent needs is present: discovery semantics, pagination loop, filter meanings, and how to escalate to the detail tool. Return values are left to the output schema, which is correct.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: all ten arguments are documented, including the enum values for sorting_mode and frequencies, the ISO 8601 format with a concrete example (2026-12-31T00:00:00Z), the inclusivity wording for resolution_time_start/end, and the pagination contract for next_token.

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 ("Browse event contracts (prediction-market events)") and immediately scopes it as paged browsing. It actively distinguishes itself from siblings, noting that get_event_details takes the eventSymbol for outcomes and that get_event_contract_bars takes a different "-EVENT" id.

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?

Gives clear routing context: use get_event_categories to source category values, use get_event_details for outcomes/pricing once an eventSymbol is known, and re-call with next_token for further pages. It stops short of an explicit when-not-to-use statement, but the workflow placement is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server