io.github.benjamin-di/earnings-watch

Earnings Documents

earnings_documents

Read-onlyIdempotent

Retrieves official earnings result-document links with verification status, letting you confirm which filings are authenticated before relying on them.

Instructions

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

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

Input Schema

Name	Required	Default
`limit`	No
`roles`	No
`scope`	No	following
`since`	No
`tickers`	No
`event_ids`	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.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond that: it does not explain what "verification status" means, how the default scope="following" affects results, what limit=100 truncates, or whether results are ordered or paginated.

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 front-loaded and free of padding, which is good, but it is under-specified for a six-parameter tool. The unexplained "R0." prefix wastes the most prominent position in the description.

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. However, with six undocumented parameters, a non-obvious default scope, and eight closely related siblings, the definition leaves too much for the agent to guess at call time.

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

Parameters1/5

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

Schema description coverage is 0% across six parameters (limit, roles, scope, since, tickers, event_ids), and the description mentions none of them. Names like "scope" with default "following" and "roles" are opaque without documentation, so the description fails to compensate for the coverage gap.

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 specific verb and resource: "List official result-document links and their verification status." An agent knows exactly what comes back. It does not differentiate itself from siblings such as earnings_get_events or earnings_status, and the leading "R0." token is unexplained noise rather than clarification.

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 use this tool versus the eight sibling tools, no prerequisites, and no exclusions. An agent must infer from the name alone that this is the document-links listing rather than the events or status endpoints.

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

Deploy Server