Skip to main content
Glama

SchedJoules Calendars

Subscribe link

get_subscribe_link
Read-onlyIdempotent

The link that adds a calendar to the user's own calendar app (Google, Apple, Outlook) through the SchedJoules app and keeps it up to date. Give it to the user to open on their phone.

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

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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by explaining that the link is a live subscription that 'keeps it up to date', which tells the agent the URL is persistent and self-refreshing rather than a one-off snapshot. It does not mention link expiry or whether the link is shareable, which keeps it from a 5.

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 no filler; the identity of the resource is front-loaded and the practical instruction follows. The opening clause is slightly convoluted as a sentence fragment, but nothing is wasted.

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 single-parameter read tool with no output schema, the description covers what the returned value is, which platforms it targets, and how the agent should present it. The only real gap is link lifetime/shareability, which is a minor omission rather than a blocking one.

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?

Schema description coverage is 100%, and the calendar_id property already documents both the source (search_calendars) and the alternate format (the number in a schedjoules.com/calendar/<id> link). The description adds nothing further about the parameter, so the baseline 3 is appropriate when the schema does the work.

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 says exactly what the tool produces: a subscription link that adds a calendar to the user's own calendar app via SchedJoules and keeps it updated. It names the supported apps (Google, Apple, Outlook), which is genuinely differentiating. It is a noun phrase rather than a verb+resource construction and does not explicitly contrast itself with search_calendars, so it falls just short of a 5.

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?

'Give it to the user to open on their phone' gives concrete hand-off guidance for the result, and the schema ties the input back to search_calendars. However, there is no explicit statement of when to use this versus pulling events with get_upcoming_events, nor any prerequisite or exclusion. Usage is implied rather than spelled out.

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