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 Calendar Plan

earnings_calendar_plan
Read-onlyIdempotent

Plan optional Outlook calendar operations for earnings events, including selected event IDs, then apply them through your external Outlook app.

Instructions

R0. Plan optional Outlook operations. Apply through your external Outlook app.

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

Input Schema

NameRequiredDescriptionDefault
fullNo
sinkNodelegated
event_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful context by framing it as planning "optional" operations that must be applied externally, but it does not explain what the plan contains, whether it depends on existing calendar state, or what applying it entails.

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 description is short and the planning-versus-applying distinction is front-loaded. However, the leading "R0." token is unexplained and adds no meaningful information, making the text feel like an internal marker rather than agent-facing guidance.

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?

Although an output schema exists, the description still leaves an agent unable to determine what the plan is for, what the parameters mean, or how this tool fits with its siblings. For a three-parameter planning tool in a large earnings-calendar toolset, that is a substantial gap.

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?

The input schema has three parameters with zero description coverage, and the description does not mention any of them. An agent gets no explanation of what "full," "sink," or "event_ids" control, so the description entirely fails to compensate for the schema gap.

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 description gives a generic verb and resource ("Plan optional Outlook operations"), so an agent can infer it produces a plan rather than executing changes. However, it does not specify what an earnings calendar plan contains, how it relates to the sibling earnings tools, or what the cryptic "R0" prefix means.

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 only usage guidance is "Apply through your external Outlook app," which hints that this tool does not perform the operations itself. It does not say when to use this planner versus earnings_calendar_ack, earnings_upcoming, or other calendar-related siblings, nor when it should be avoided.

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