io.github.benjamin-di/earnings-watch

Earnings Watch

earnings_watch

Idempotent

Follow an issuer to track upcoming earnings and resolve ambiguous tickers by returning candidate matches.

Instructions

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

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": {
      "ticker": "<ticker>"
    },
    "name": "earnings_watch"
  }
}

Input Schema

Name	Required	Description	Default
`isin`	No
`name`	No
`ticker`	Yes
`exchange`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 3, 2026

TDQS

C2.2/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation, so safety is covered. The description adds two genuinely useful traits beyond that: the subscription is scoped to the caller ("for yourself") and that an ambiguous ticker yields candidate matches rather than an error or a write. It does not say what confirming a candidate requires or whether a follow persists across sessions.

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

Conciseness2/5

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

It is short, but brevity here comes from under-specification rather than economy. The unexplained "R1." prefix burns the prime opening slot and the key scoping word "for yourself" is buried mid-sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, but for a state-changing follow tool with four undocumented parameters, the definition leaves out what gets created, whether re-following is safe beyond the idempotent hint, and how to act on the returned candidates.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description carries full burden for explaining ticker, isin, name, and exchange. It says nothing about the optional disambiguators or how ticker combined with exchange or isin is resolved, only that ambiguity returns candidates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Follow an issuer for yourself" signals a per-user subscription action but never states what is being watched (earnings events for a ticker) or how it differs from the sibling tools earnings_watchlist, earnings_unwatch, or earnings_get_events. The leading token "R1." is unexplained boilerplate that adds no meaning for an agent.

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

Usage Guidelines2/5

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

The only actionable hint is that ambiguous tickers return candidates, which describes a fallback behavior rather than when to use this tool. There is no stated condition distinguishing it from earnings_watchlist or earnings_unwatch, so an agent must guess which is the add versus list versus remove path.

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

Deploy Server