Skip to main content
Glama
Sign In
io.github.benjamin-di/earnings-watch

io.github.benjamin-di/earnings-watch

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Earnings Get Events

earnings_get_events
Read-onlyIdempotent

Retrieve up to 20 public earnings events by ID, including supporting evidence and bounded revision history for verification.

Instructions

R0. Read up to 20 public events with evidence and bounded history.

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": {
      "ids": "<ids>"
    },
    "name": "earnings_get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine behavioral facts beyond that: a hard cap of 20 items, that only public events are returned, and that results carry evidence plus a bounded history. It says nothing about what happens with more than 20 ids or whether ordering is guaranteed.

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?

A single short sentence with no wasted clauses, which is good, but the leading "R0." is dead weight that consumes the most salient position. The remaining content is front-loaded but too compressed to be informative.

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-value documentation is not strictly required, but for a one-parameter lookup with 0% schema coverage the definition omits the essentials: what an event is, what ids are accepted, and how it relates to the sibling earnings tools. It is not sufficient on its own to invoke the tool confidently.

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?

There is one required parameter, "ids", and schema description coverage is 0%, so the description must carry the meaning. It never mentions ids at all — not their format, whether they are event ids, or how the 20-item cap interacts with the array length.

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?

"Read up to 20 public events with evidence and bounded history" gives a verb and a resource plus a result cap, so the general shape is inferable, but "events" is undefined and "R0" is an unexplained internal label that conveys nothing. Nothing in the sentence distinguishes it from siblings like earnings_upcoming, earnings_changes, or earnings_documents.

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 description never states when to call this versus the eight sibling earnings tools, nor any prerequisite such as needing known ids. The only implicit cue is the 20-item cap, which hints at batch lookup but does not guide selection.

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

Deploy Server

Other Tools