Skip to main content
Glama

SchedJoules Calendars

Upcoming events

get_upcoming_events
Read-onlyIdempotent

The next events on a calendar: at most 5 in the next 60 days, with title and start. For a folder of calendars, its calendars instead.

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": {
      "calendar_id": "<calendar_id>"
    },
    "name": "get_upcoming_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendar_idYesThe calendar id from search_calendars, or the number in a schedjoules.com/calendar/<id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the safety profile is pre-supplied. The description adds genuinely new behavioral facts: results are truncated to at most 5 events, the window is 60 days, only title/start are returned, and folder ids behave differently. It does not say what happens with zero events or whether the cap is a hard truncation versus a filter.

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?

Two short sentences with the primary behavior and its limits front-loaded; nothing is wasted. The second sentence is telegraphic ('its calendars instead') and requires a re-read to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with no output schema, the description covers the essential return shape (title and start), the count and time bounds, and the folder edge case. Remaining gaps — empty-result behavior and the exact folder response format — are modest.

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

Parameters3/5

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

With a single parameter and 100% schema description coverage, the schema already explains calendar_id, its pattern, and its source. The description adds only an indirect hint that the id may refer to a folder of calendars, which the schema does not mention, but it does not spell out that consequence clearly.

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+resource ('the next events on a calendar') plus concrete scope limits ('at most 5 in the next 60 days') and returned fields ('title and start'). It also flags a variant behavior for folders. It stops short of naming or contrasting the siblings (search_calendars, get_subscribe_link), though those are self-evidently different functions.

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?

Usage is implied rather than stated: an agent can infer this is for 'what's coming up on calendar X'. There is no explicit when-to-use/when-not statement and no note that the calendar id must first come from search_calendars (that lives only in the schema). The folder clause is a behavior variant, not alternative-selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources