io.github.benjamin-di/earnings-watch

Earnings Unwatch

earnings_unwatch

Idempotent

Removes a ticker from your manual earnings watchlist while retaining its public history, so you can stop following an issuer without deleting past data.

Instructions

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

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_unwatch"
  }
}

Input Schema

Name	Required	Description	Default
`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.6/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 mutation. The description adds one genuinely useful behavioral fact beyond them: only the manual follow is removed while public history is retained, which bounds the blast radius. It still omits error behavior for unwatched tickers and any confirmation/return semantics, so it goes beyond annotations but not far.

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

Conciseness3/5

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

The operative sentence is short and front-loaded, but the unexplained "R1." label consumes the first tokens without informing the agent. One clause does real work (history retained); the rest is under-specified rather than tight.

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 described. That said, this is a state-changing tool with zero parameter documentation and no note on required inputs, failure modes, or confirmation behavior, leaving an agent materially under-informed before invoking it.

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% for two parameters, so the description carries the full burden and does not meet it. Neither the required ticker nor the optional exchange is mentioned, and no format or null-handling guidance is given. Only the vague phrase "your manual follow" hints that the follow is scoped per user and instrument.

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

Purpose3/5

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

"Remove your manual follow" names the action and scopes it to the manual follow, which is more than the name alone conveys. However, it never says what is being unwatched (a ticker/company), and the cryptic "R1." prefix adds no meaning. An agent can infer it is the inverse of earnings_watch, but the description does not make that explicit.

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?

There is no when-to-use guidance, no mention of the sibling earnings_watch as the counterpart, and no statement about what happens when the ticker is not currently followed. Usage must be inferred entirely from the name.

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

Deploy Server