Skip to main content
Glama

MetricDuck — Financial Analysis

by com.metricduck
OverviewDiscussionsAdmin

IR Event Calendar

get_company_events
Read-only

Retrieve a company's IR event CALENDAR — UPCOMING and PAST investor-relations events (earnings calls, annual/shareholder meetings, broker conferences, investor days) with the materials attached to each (deck, webcast, press release, transcript).

Reach for this for calendar questions:

  • "When does {ticker} next report / hold its earnings call?" → the UPCOMING list (scheduled events)

  • "What IR events did {ticker} have this year?" / "was {ticker} at any conferences?"

  • "What materials are attached to {ticker}'s last earnings event?"

Each event has: occurred_at (issuer-local datetime) + time_precision, event_type (verbatim/open vocab), the verbatim source title, and material chips — each material's material_id is the get_ir_documents doc_id (read a deck's slide TEXT with get_ir_documents, not here).

Coverage is honest: if a company hasn't been harvested yet, that is stated — an empty result does NOT mean the company has no IR events. last_checked_at stamps the calendar's as-of time (events announced since are not shown). When the calendar has no events, the company's results announcements filed with the SEC (8-K Item 2.02 — usually the quarterly earnings release; last 24 months) are listed instead — past filing dates that show its reporting cadence, not a scheduled date.

What management SAID on earnings calls (guidance/tone by quarter) → compare_earnings_calls.

Not point-in-time: upcoming vs past is relative to today; for as-of work use a tool that takes vantage_date (e.g. list_filings, get_earnings).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesCompany ticker symbol (e.g., 'AAPL'). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety, but the description adds crucial behavioral context: empty results do not mean no IR events, last_checked_at defines freshness, fallback to 8-K Item 2.02 filings, and the non-point-in-time nature of upcoming vs past buckets. These are beyond what the annotations provide.

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

Conciseness5/5

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

The description is long but tightly structured and front-loaded, with bullets for common questions, return fields, coverage caveats, and alternatives. Every section carries routing or caveat information that helps correct invocation.

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?

Although there is no output schema, the description enumerates the returned event fields, material chip semantics, freshness metadata, fallback behavior, and point-in-time limitations. This is complete enough for an agent to call the tool correctly and interpret its results.

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% and the sole ticker parameter is fully documented in the schema. The description does not add syntax or constraints beyond that, so the baseline of 3 for high schema coverage is appropriate.

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?

The description states a specific verb and resource: retrieve a company's IR event calendar, covering both upcoming and past events. It distinguishes itself from siblings by explicitly routing materials-text questions to get_ir_documents and management-commentary questions to compare_earnings_calls.

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

Usage Guidelines5/5

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

It gives explicit example questions that select this tool, explains when the fallback SEC filing list appears, and names alternative tools for adjacent needs. The when-to-use guidance is concrete and leaves little ambiguity.

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

All MetricDuck — Financial Analysis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources