Skip to main content
Glama
Sign In
Local DevLog MCP

Local DevLog MCP

by Kyoungwoong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

validate_calendar_connection

Idempotent

Check Apple Calendar permission status and configured target, and optionally request the macOS full-access prompt to resolve access issues.

Instructions

Inspect Apple Calendar permission and configured target. Set requestPermission only when the user wants the macOS full-access prompt.

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

Input Schema

NameRequiredDescriptionDefault
requestPermissionNo

Output Schema

NameRequiredDescriptionDefault
okYes
codeNo
resultNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / result / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.4.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations mark this non-read-only, idempotent and open-world, but do not explain why a read-only-sounding 'inspect' is not read-only. The description supplies that context: setting requestPermission triggers the macOS full-access prompt. That is exactly the behavioral detail annotations alone cannot convey. It does not mention permission-denied outcomes or the resulting state, so not 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.

Conciseness5/5

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

Two short sentences, no filler. The primary action is front-loaded and the conditional parameter guidance follows.

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?

An output schema exists, so return values need not be explained. For a one-optional-boolean diagnostic tool, the description covers purpose and the one non-obvious behavioral effect. A brief note on what happens when permission is not granted would make it complete.

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?

Schema coverage is 0% and the parameter name is opaque, so the description carries the burden. It tells the agent what requestPermission does (triggers the macOS full-access prompt) and the condition for setting it. It omits that it is optional with a default of false, which the schema already shows.

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?

Uses a specific verb+resource: 'Inspect Apple Calendar permission and configured target.' An agent can tell this is a pre-flight diagnostic rather than the publishing siblings (preview_calendar_publication, publish_to_calendar). It stops short of naming those siblings explicitly.

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?

The second sentence gives a clear condition for when to set requestPermission, but there is no guidance on when to call the tool itself (e.g., before publishing) or what to do with the result. Usage is implied by the surrounding calendar-publish family 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