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 Status

earnings_status
Read-onlyIdempotent

Retrieve catalogue counts and maintenance status without model calls to verify earnings data availability before querying.

Instructions

R0. Read catalogue counts and maintenance status without model calls.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3/5.0
Behavior3/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 fully covered by structured data. The description's one genuine addition is that this call incurs no model invocations, which is useful cost/latency context. It does not say whether "maintenance status" can change mid-session or what degraded/in-maintenance looks like in the response.

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?

It is a single short sentence, which is efficient, but the leading "R0" token is unexplained jargon that consumes attention without adding meaning. The useful constraint ("without model calls") is tacked on at the end rather than front-loaded.

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 no explanation, and the annotations cover safety. Still, for a tool sitting among nine similarly named earnings_* tools, the description never clarifies what is being counted or when an agent should prefer it over earnings_get_events or earnings_upcoming. It is minimally adequate but leaves real routing gaps.

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, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies a call with no arguments.

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 catalogue counts and maintenance status" gives a verb and two resource-ish objects, so the agent can infer a status/inventory read. But "catalogue" is never defined (catalogue of what — events, documents, watchlists?), and the cryptic "R0" prefix conveys nothing without external context. Nothing distinguishes it from the nine earnings_* siblings.

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 explicit when-to-use statement and no named alternative among the siblings. The phrase "without model calls" hints at a cheap pre-check before heavier calls, but that inference is left entirely to the agent rather than stated.

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