Equibles

Browse Investor Events

ListInvestorEvents

Read-only

List a company's investor events, newest first: earnings calls plus conferences, investor days and shareholder meetings. Each row gives the event id, type, UTC start, title, fiscal period (earnings calls only), status, and each material's status (available, pending, notPublished, failed, notAttempted, noCallHeld) for transcript, audio and slides. Read a conference by event id with GetInvestorEventTranscript; GetEarningsCallEvent is keyed by fiscal quarter.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of events to return (default 25, max 100; values outside 1-100 are clamped)
`offset`	No	Number of matching events to skip before returning rows (default 0)
`ticker`	Yes	Company ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US.
`eventType`	No	Optional event type to filter on: EarningsCall, CapitalMarketsDay, InvestorUpdate, AGM, Conference, FiresideChat, or MAndA (default: all types)
`includeUncaptured`	No	Also list events hidden because none of their materials could be captured and still on the company's own IR calendar (default false); their status reads Unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedInput schema / properties / includeUncaptured

Added value: +{
+  "default": false,
+  "description": "Also list events hidden because none of their materials could be captured and still on the company's own IR calendar (default false); their status reads Unavailable.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / ticker / description

Previous value: -"Company ticker symbol (e.g., AAPL, MSFT)"New value: +"Company ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US."

Changed1 schema field changedSep 3, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Number of matching events to skip before returning rows (default 0)",
+  "type": "integer"
+}

First observedJul 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real behavioral detail on top — sort order, the exact row fields returned, the material-status vocabulary, and that fiscal period applies only to earnings calls. It stops short of describing pagination interaction or how many events a typical company yields.

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?

Three sentences, front-loaded with the verb and resource, then the return shape, then the routing hints. It is dense rather than bloated, though the enumerated status vocabulary in the middle sentence makes it slightly heavy to scan.

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?

There is no output schema, so the description carries the full burden of describing returns — and it does so thoroughly, listing every row field and the full status enumeration for transcript, audio and slides. An agent has enough to select and call this tool correctly.

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 description coverage is 100%, so limit, offset, ticker, eventType and includeUncaptured are already fully documented; the description adds no parameter syntax or format detail beyond what the schema provides. Baseline 3 applies 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?

Specific verb + resource ('List a company's investor events'), with the exact scope enumerated (earnings calls, conferences, investor days, shareholder meetings) and the ordering stated ('newest first'). It also names the sibling tools that consume its output, so an agent can place it in the workflow without opening any schema.

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?

Explicit routing guidance: read an event via GetInvestorEventTranscript, and note that GetEarningsCallEvent is keyed by fiscal quarter rather than by event id. That is unusually actionable. It does not, however, distinguish this tool from the sibling GetUpcomingInvestorEvents (upcoming vs. historical scope) or state any exclusions.

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

All Equibles tools Inspect

Try in Browser