Skip to main content
Glama

My calendar feed link

deputy_get_my_calendar_url
Read-only

Confirms whether your personal Deputy calendar feed is configured, without exposing the secret feed URL. Use it to verify setup before reading shifts from the roster.

Instructions

Confirm that your personal calendar feed is configured. The feed link itself is a secret in this mode and is never shown.

When NOT to use: to read the shifts in the feed (use deputy_get_my_roster).

Returns markdown or, with response_format="json", an object {"mode", "configured", "calendar_url"}.

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": "deputy_get_my_calendar_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_formatNoOutput format: 'markdown' (human-readable, default) or 'json' (raw records).markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is read-only and open-world. The description adds important behavior beyond them by stating that the feed link is secret and never shown, though the returned calendar_url field creates minor ambiguity about what is actually exposed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and structured into purpose, when-not-to-use, and return format. Every sentence contributes useful information without waste.

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?

The tool is simple and an output schema exists, so return values need not be explained in depth. The description still covers configuration checking, secret handling, and the main alternative, though the calendar_url return field remains slightly ambiguous.

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 coverage is 100% and the single response_format parameter is fully documented by the schema. The description reinforces its effect on return shape but adds little parameter semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and scope: confirm that the personal calendar feed is configured. It also distinguishes this from reading shifts by naming deputy_get_my_roster explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not-to-use case and points to the correct alternative, deputy_get_my_roster. The first sentence also implies when to use it: checking whether the calendar feed is configured.

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