Skip to main content
Glama
io.github.benjamin-di/earnings-watch

io.github.benjamin-di/earnings-watch

by benjamin-di

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Verified earnings facts are shared. Follows and calendar state belong to you. Dates without verified clocks remain all-day. Calendar updates are optional: use the external Outlook app to apply a plan, then acknowledge only confirmed operations. Never add attendees.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
earnings_upcomingC

R0. List upcoming verified dates, including explicit timing uncertainty.

earnings_get_eventsC

R0. Read up to 20 public events with evidence and bounded history.

earnings_documentsC

R0. List official result-document links and their verification status.

earnings_changesB

R0. Read the shared change feed; keep the returned cursor for next time.

earnings_watchlistB

R0. Read your follows and pending registration states.

earnings_watchC

R1. Follow an issuer for yourself; ambiguous tickers return candidates.

earnings_unwatchC

R1. Remove your manual follow; public history is retained.

earnings_calendar_planC

R0. Plan optional Outlook operations. Apply through your external Outlook app.

earnings_calendar_ackC

R1. Record confirmed external operations; reject stale or altered plans.

earnings_statusB

R0. Read catalogue counts and maintenance status without model calls.

Prompts

Interactive templates invoked by user choice

NameDescription
earnings_briefingSummarize the coming week's verified earnings milestones.
results_briefSummarize results coverage from verified documents.
sync_to_my_outlookApply an optional earnings calendar plan through the external Outlook app.

Resources

Contextual data attached and managed by the client

NameDescription
upcoming_ics

TDQS

B3/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a distinct role: events, upcoming dates, documents, change feed, watchlist, follow/unfollow, calendar planning/acknowledgment, and status. The read-only public-data tools are clearly separated by resource, and the write tools are clearly separated by action. No two tools appear to do the same thing.

Naming Consistency3/5

All tools use the same earnings_ prefix and snake_case, which keeps them readable. However, the suffix conventions are mixed: get_events is verb_noun, upcoming/documents/changes/watchlist/status are noun-oriented, and watch/unwatch/calendar_plan/calendar_ack mix action and object styles. The pattern is understandable but not consistently verb_noun.

Tool Count5/5

Ten tools is a well-scoped set for an earnings-watch service. It covers reads, follows, change tracking, calendar coordination, and status without obvious redundancy. Each tool appears to earn its place.

Completeness4/5

The surface covers the core lifecycle: upcoming dates, events, documents, change feed, watchlist, follow/unfollow, calendar plan/ack, and status. Minor gaps may exist around explicit event search/filtering or calendar cancellation, but agents can likely work around them. Overall coverage is strong for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues