io.github.benjamin-di/earnings-watch

Earnings Changes

earnings_changes

Read-onlyIdempotent

Read the shared earnings change feed and return a cursor to resume from on the next request, so clients can track updates incrementally.

Instructions

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

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

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 3, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already establish a safe, read-only, idempotent operation, while the description adds the shared-feed and cursor-persistence behavior. It does not clarify feed ordering, cursor advancement or invalidation, or whether reading affects a shared consumer position.

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

Conciseness4/5

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

The single sentence is compact and places the operation before the continuation advice. The unexplained "R0." adds no usable meaning, and the cursor clause could name the parameter directly.

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?

The output schema reduces the need to document return fields, and the annotations cover safety, but the definition still omits the feed's content scope and basic invocation flow. It is minimally actionable with defaults, yet important gaps remain around initial cursor use, continuation, and sibling selection.

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?

With 0% schema description coverage, the description only indirectly explains `cursor` by saying to keep the returned cursor for next time; it never explicitly says to pass that value back through the parameter. `limit` receives no semantic guidance beyond its integer type and default in the schema.

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

Purpose4/5

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

The description gives a concrete action and resource—"Read the shared change feed"—which fits earnings_changes and broadly distinguishes a feed read from event or document retrieval. It does not explain what kinds of earnings changes are included or explicitly differentiate the sibling tools.

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

Usage Guidelines3/5

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

Keeping "the returned cursor for next time" implies repeated incremental consumption and provides useful continuation advice. There is no guidance on when to choose this over earnings_get_events, earnings_upcoming, or earnings_status, nor on first-call versus resumed-call usage.

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

Deploy Server