io.github.benjamin-di/earnings-watch

Earnings Watchlist

earnings_watchlist

Read-onlyIdempotent

Read followed issuers and pending registration states to verify earnings tracking status and identify registrations still needing action.

Instructions

R0. Read your follows and pending registration states.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "earnings_watchlist"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 3, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes only the notion that the result includes both followed items and 'pending registration states', which is useful but thin; it says nothing about ordering, scope, or what a pending state means.

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 single sentence is short and front-loaded, but the cryptic 'R0' prefix consumes attention without conveying meaning and should be removed or explained. Little else is wasted, but little else is present.

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

Completeness3/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, and the empty input schema needs no elaboration. What remains missing is how this read-only view relates to the mutation siblings earnings_watch and earnings_unwatch, which is the main thing an agent would need to choose correctly.

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

Parameters4/5

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

The tool takes zero parameters and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

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?

The verb 'Read' and the objects 'follows' and 'pending registration states' give a rough sense of the resource, but the leading token 'R0' is unexplained and 'follows' overlaps ambiguously with the sibling tools earnings_watch and earnings_unwatch. An agent cannot confidently distinguish this read-only listing from the watch/unwatch mutations without guessing.

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 statement of when to call this tool versus earnings_watch, earnings_unwatch, earnings_status, or any other sibling. The only implied usage is the bare contrast between 'reading' follows and 'registering' them, which the agent must infer.

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

Deploy Server